LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44986: ipv6: fix possible UAF in ip6_finish_output2()

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible UAF in ip6_finish_output2() If skb_expand_head() returns NULL, skb has been freed and associated dst/idev could also have been freed. We need to hold rcu_read_lock() to make sure the dst and associated idev are alive.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel IPv6 memory-safety flaw. Under a specific packet-buffer failure path, the kernel could reference network-routing data after it was freed. The provided sources do not give CVSS, practical impact, or evidence of exploitation.

Executive priority

Handle through normal kernel patch management, with elevated attention for exposed Linux infrastructure using IPv6. There is not enough evidence here to justify emergency response without a vendor severity rating or exploitation signal.

Technical view

CVE-2024-44986 is a possible use-after-free in ip6_finish_output2(). If skb_expand_head() returns NULL, the skb is freed and associated dst/idev may also be freed. The kernel fix holds rcu_read_lock() so those objects remain valid during use.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with relevant IPv6 networking paths. The CVE record lists Linux kernel versions and stable commits, but distribution backports may change package-level status.

Exploitation context

The provided bundle shows no CISA KEV listing and no cited source claiming active exploitation. It also does not describe attacker prerequisites, exploit reliability, or whether this is remotely triggerable in practice.

Researcher notes

The key condition is skb_expand_head() failure in the IPv6 output path, followed by potentially stale dst/idev access. Review fixed stable commits for exact affected ranges and whether downstream distributions backported the RCU protection.

Mitigation direction

  • Apply kernel updates from the Linux stable tree or your distribution vendor.
  • Check Debian LTS and other vendor advisories for backported fixes.
  • Prioritize systems using IPv6 or exposed network services until vendor severity is known.
  • Avoid treating upstream version numbers as definitive for distro kernels.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and containers hosts.
  • Compare installed kernels against vendor advisories and listed stable commits.
  • Confirm whether IPv6 is enabled and used on exposed systems.
  • Track vendor CVSS or severity if later published.
Prepared
Confidence
medium
Sources
8

Public sources used

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-44986 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5796015fa968a3349027a27dcd04c71d95c53ba5, 5796015fa968a3349027a27dcd04c71d95c53ba5, 5796015fa968a3349027a27dcd04c71d95c53ba5, 5796015fa968a3349027a27dcd04c71d95c53ba5, 5796015fa968a3349027a27dcd04c71d95c53ba5, ded37d03440d0ab346a8287cc2ba88b8dc90ceb0, 2323690eb05865a657709f4d28eb9538ea97bfc2, b34c668a867ffdcf8bd8db4a36512572e82b4a15, 5.4.137, 5.10.55, 5.13.7unaffected
LinuxLinux5.14, 0, 5.15.166, 6.1.107, 6.6.48, 6.10.7, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.