CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit()
In the Linux kernel, the following vulnerability has been resolved:
ipv6: prevent possible UAF in ip6_xmit()
If skb_expand_head() returns NULL, skb has been freed
and the associated dst/idev could also have been freed.
We must use rcu_read_lock() to prevent a possible UAF.
Security readout for executives and security teams
Plain-English summary
A Linux kernel IPv6 transmission flaw can leave networking code referencing memory that has already been freed. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as critical. Actual exposure depends on the running kernel and whether its vendor package contains the upstream correction.
Executive priority
Treat as an urgent patch-validation issue because the supplied severity is critical and the flaw affects kernel memory safety. Prioritize confirmed affected systems, but avoid declaring an incident solely from version detection because active exploitation is not evidenced and vendors may have backported the fix.
Technical view
In ip6_xmit(), skb_expand_head() may fail and free the skb plus associated dst or idev objects. Subsequent access could therefore cause a use-after-free. The upstream correction adds RCU read-side protection to keep associated objects valid during the affected operation.
Likely exposure
Potentially exposed assets are Linux systems running the listed affected kernel versions, including 5.15, 5.15.166, 6.1.107, 6.6.48, 6.10.7, and 6.11. Distribution kernels may backport fixes, so version strings alone are not conclusive.
Exploitation context
The supplied CVSS vector describes network-reachable, low-complexity exploitation without privileges or user interaction. However, the bundle reports that this CVE is not in KEV and provides no evidence of active exploitation, public exploit availability, or demonstrated impact.
Researcher notes
The record identifies the failure path and RCU-based correction but does not provide reproducibility conditions, affected configuration requirements, or exploitation evidence. The version data contains commit identifiers, duplicate entries, and an anomalous "0" value; validate exposure against upstream commits and distribution advisories rather than relying on simple version comparison.
Mitigation direction
Apply vendor-supported kernel updates incorporating the linked upstream stable fixes.
Review the Linux distribution's advisory and package status for backported corrections.
Prioritize externally exposed and operationally critical Linux systems.
Follow vendor guidance where package fix status remains unclear.
Validation and detection
Inventory running kernel versions across Linux hosts.
Check vendor package changelogs for CVE-2024-44985 or linked fixes.
Confirm the active kernel, not merely the installed package, contains the correction.
Re-scan updated systems and document unresolved vendor-package ambiguity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-44985 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.