LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36903: ipv6: Fix potential uninit-value access in __ip6_make_skb()

In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix potential uninit-value access in __ip6_make_skb() As it was done in commit fc1092f51567 ("ipv4: Fix uninit-value access in __ip_make_skb()") for IPv4, check FLOWI_FLAG_KNOWN_NH on fl6->flowi6_flags instead of testing HDRINCL on the socket to avoid a race condition which causes uninit-value access.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-36903 is a Linux kernel IPv6 bug involving possible use of uninitialized data during packet creation. The public record does not provide a CVSS score, impact rating, or confirmed exploitation. Treat it as a kernel maintenance priority, especially for Linux systems, appliances, and products that rely on IPv6 networking.

Executive priority

Prioritize within normal kernel patch cycles unless vendor advisories identify critical exposure in your environment. Escalate for externally exposed infrastructure, managed appliances, and products where kernel update windows are infrequent.

Technical view

The fix changes __ip6_make_skb() to check FLOWI_FLAG_KNOWN_NH in fl6->flowi6_flags rather than socket HDRINCL state, avoiding a race condition that can lead to uninitialized-value access. The issue mirrors an earlier IPv4 fix. Public sources list upstream stable commits and downstream advisories, but not detailed exploit prerequisites.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions or vendor products that include those kernels. IPv6-capable servers, embedded systems, and network appliances should be inventoried. The source bundle does not prove exposure for all Linux distributions because vendor backports may change version appearances.

Exploitation context

The CVE is not marked in KEV, and the supplied sources do not cite active exploitation or public weaponization. The available evidence describes a race-condition bug and upstream fixes, not a confirmed attack path. Operational risk should be based on kernel exposure and vendor applicability.

Researcher notes

Key unknowns are severity, attack preconditions, and practical exploitability. Analysis should focus on whether local builds contain the __ip6_make_skb() fix and whether vendor kernels backported it. Avoid assuming exploitability beyond the documented uninitialized-value race condition.

Mitigation direction

  • Apply vendor-supported kernel updates that include the upstream stable fix.
  • Check Debian LTS and Siemens advisories if those products apply.
  • Use distribution advisories rather than upstream version strings alone.
  • Prioritize internet-facing or appliance-like Linux systems with IPv6 enabled.
  • Monitor vendor guidance for severity changes or backported fixes.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and containers hosts.
  • Map affected assets against vendor advisories and package changelogs.
  • Confirm whether installed kernels include the referenced stable commits or backports.
  • Verify Debian LTS or Siemens product applicability where relevant.
  • Record systems deferred from patching and the vendor rationale.
Prepared
Confidence
medium
Sources
10

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-36903 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
3ADP providers
9Source 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux605b056d63302ae84eb136e88d4df49124bd5e0d, d65ff2fe877c471aa6e79efa7bd8ff66e147c317, 2c9cefc142c1dc2759e19a92d3b2b3715e985beb, ea30388baebcce37fd594d425a65037ca35e59e8, ea30388baebcce37fd594d425a65037ca35e59e8, ea30388baebcce37fd594d425a65037ca35e59e8, 165370522cc48127da564a08584a7391e6341908, f394f690a30a5ec0413c62777a058eaf3d6e10d5, 0cf600ca1bdf1d52df977516ee6cee0cadb1f6b1, 02ed5700f40445af02d1c97db25ffc2d04971d9f, 5.10.178, 5.15.107, 6.1.24, 4.14.313, 4.19.281, 5.4.241, 6.2.11unaffected
LinuxLinux6.3, 0, 5.10.248, 5.15.198, 6.1.140, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

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