CVE-2024-36017: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation
In the Linux kernel, the following vulnerability has been resolved:
rtnetlink: Correct nested IFLAVFVLANLIST attribute validation
Each attribute inside a nested IFLAVFVLANLIST is assumed to be a struct iflavfvlaninfo so the size of such attribute needs to be at least of sizeof(struct iflavfvlaninfo) which is 14 bytes. The current size validation in dosetvfinfo is against NLAHDRLEN (4 bytes) which is less than sizeof(struct iflavfvlaninfo) so this validation is not enough and a too small attribute might be cast to a struct iflavfvlaninfo, this might result in an out of bands read access when accessing the saved (casted) entry in ivvl.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
rtnetlink: Correct nested IFLAVFVLANLIST attribute validation
The Linux kernel CVE team has assigned CVE-2024-36017 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024053015-CVE-2024-36017-bf96@gregkh/T
— Red Hat
Linux Kernel is vulnerable to a denial of service, caused by an out-of-bounds read when accessing the saved (casted) entry in ivvl. A local authenticated attacker could exploit this vulnerability to cause a denial of service.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-36017?
The severity of CVE-2024-36017 is classified as high due to its impact on Linux kernel security.
How do I fix CVE-2024-36017?
To fix CVE-2024-36017, upgrade to the kernel versions 4.19.314, 5.4.276, 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.8.10, or 6.9, or the specified Debian versions.
What platforms are affected by CVE-2024-36017?
CVE-2024-36017 affects various versions of the Linux kernel on both Red Hat and Debian platforms.
What is the nature of the vulnerability CVE-2024-36017?
CVE-2024-36017 is a vulnerability in the Linux kernel related to improper validation of nested IFLA_VF_VLAN_LIST attribute.
Are there any workarounds for CVE-2024-36017?
There are no specific workarounds for CVE-2024-36017; applying the recommended kernel updates is the best mitigation.