LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36971: net: fix __dst_negative_advice() race

In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-36971 is a Linux kernel use-after-free flaw in networking code. A local user with low privileges could potentially gain high-impact control over confidentiality, integrity, or availability. CISA lists it in KEV, so exploitation is supported by a government source. Treat affected Linux systems as urgent, especially shared servers and container hosts.

Executive priority

Prioritize remediation this cycle for affected Linux systems. The issue requires local access, but KEV status raises urgency because exploitation is confirmed by CISA. Focus first on shared infrastructure where one compromised account or workload could threaten the host kernel.

Technical view

The bug is an RCU ordering race in __dst_negative_advice() when clearing sk->sk_dst_cache. The vulnerable path releases the old dst before correctly clearing the socket cache, creating a possible use-after-free. The CVE notes the issue became visible with UDP sockets and is fixed by upstream Linux stable commits across branches.

Likely exposure

Exposure is local rather than network-direct: attackers need some local execution context. Highest concern is multi-user Linux, CI runners, shared hosting, container hosts, and systems where untrusted workloads run on the same kernel. Exact package exposure depends on the distribution kernel build and backport status.

Exploitation context

Active exploitation is supported because CISA KEV lists CVE-2024-36971. The provided sources do not include public exploit details, observed targets, or exploitation mechanics. CVSS is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high CIA impact.

Researcher notes

Do not assume every listed upstream version maps directly to distribution exposure; vendors may backport fixes without changing major kernel versions. Validate by package advisory, changelog, or kernel commit status. The public bundle identifies upstream stable commits and Debian LTS notice but does not provide exploit telemetry beyond KEV.

Mitigation direction

  • Apply distribution kernel updates that include the upstream stable fixes.
  • Reboot systems so the patched kernel is actually running.
  • Use vendor advisories to confirm exact package and branch status.
  • Prioritize shared Linux hosts, container platforms, and CI runners.
  • Where patching is delayed, restrict untrusted local accounts and workloads.

Validation and detection

  • Inventory running kernel versions across Linux servers and hosts.
  • Confirm installed packages include a fix for CVE-2024-36971.
  • Verify the active kernel after reboot, not only the installed package.
  • Check Debian LTS or distribution-specific advisories where applicable.
  • Track CISA KEV status in vulnerability management reporting.
Prepared
Confidence
high
Sources
12

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-36971 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
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
5Timeline events
2ADP providers
11Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-36971Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  4. ADP timelineCISA-ADP

    CVE-2024-36971 added to CISA KEV

  5. CVE updatedCVE Program

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

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvcother:kev
  • 2024-08-07T00:00:00.000Z: CVE-2024-36971 added to CISA KEV
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314, a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314unaffected
LinuxLinux4.6, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.94, 6.6.34, 6.9.4, 6.10affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.