LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26816: x86, relocs: Ignore relocations in .notes section

In the Linux kernel, the following vulnerability has been resolved: x86, relocs: Ignore relocations in .notes section When building with CONFIG_XEN_PV=y, .text symbols are emitted into the .notes section so that Xen can find the "startup_xen" entry point. This information is used prior to booting the kernel, so relocations are not useful. In fact, performing relocations against the .notes section means that the KASLR base is exposed since /sys/kernel/notes is world-readable. To avoid leaking the KASLR base without breaking unprivileged tools that are expecting to read /sys/kernel/notes, skip performing relocations in the .notes section. The values readable in .notes are then identical to those found in System.map.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can expose the kernel’s KASLR base address through a world-readable notes interface on affected x86 Xen PV-capable builds. By itself, this is an information leak, not a complete compromise, but it can weaken an important exploit mitigation used to make kernel attacks harder.

Executive priority

Patch through normal kernel maintenance, with higher priority for shared, multi-user, virtualized, or Xen-related Linux environments. This is a mitigation-bypass information leak, so urgency increases when paired with other kernel exposure or untrusted local users.

Technical view

When CONFIG_XEN_PV=y, x86 kernel build data places text symbols in .notes for Xen startup discovery. Relocating those entries caused /sys/kernel/notes to reveal the randomized kernel base. The fix skips relocations in .notes, leaving values equivalent to System.map and avoiding KASLR disclosure.

Likely exposure

Exposure is most relevant to affected Linux kernel versions on x86 systems built with CONFIG_XEN_PV=y where /sys/kernel/notes is readable. The bundle lists Linux kernel versions from 2.6.23 through affected stable ranges before the referenced fixes.

Exploitation context

The provided sources do not state active exploitation, and KEV is false. Practical abuse would likely support a separate local kernel exploit by reducing KASLR uncertainty. The sources do not support treating this as a remote, standalone compromise.

Researcher notes

Focus review on x86 relocation handling and /sys/kernel/notes exposure in Xen PV-enabled builds. The evidence supports KASLR base disclosure only; it does not describe exploit chains, affected downstream products beyond cited advisories, or compensating mitigations.

Mitigation direction

  • Apply the relevant stable Linux kernel update containing the referenced fix commits.
  • Use distribution or product advisories for packaged kernels and appliances.
  • Prioritize x86 Xen PV-capable systems built with CONFIG_XEN_PV=y.
  • Do not assume generic hardening replaces the kernel fix.
  • Track Debian LTS and Siemens guidance where those environments apply.

Validation and detection

  • Inventory running kernel versions against the affected and fixed source ranges.
  • Confirm whether relevant kernels are built with CONFIG_XEN_PV=y.
  • Verify updated kernels include the .notes relocation skip fix.
  • Check vendor package advisories for backported fixes.
  • Record that no cited source confirms active exploitation.
Prepared
Confidence
high
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-26816 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
13Source 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
LinuxLinux5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045, 5ead97c84fa7d63a6a7a2f4e9f18f452bd109045unaffected
LinuxLinux2.6.23, 0, 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 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.