LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26850: mm/debug_vm_pgtable: fix BUG_ON with pud advanced test

In the Linux kernel, the following vulnerability has been resolved: mm/debug_vm_pgtable: fix BUG_ON with pud advanced test Architectures like powerpc add debug checks to ensure we find only devmap PUD pte entries. These debug checks are only done with CONFIG_DEBUG_VM. This patch marks the ptes used for PUD advanced test devmap pte entries so that we don't hit on debug checks on architecture like ppc64 as below. WARNING: CPU: 2 PID: 1 at arch/powerpc/mm/book3s64/radix_pgtable.c:1382 radix__pud_hugepage_update+0x38/0x138 .... NIP [c0000000000a7004] radix__pud_hugepage_update+0x38/0x138 LR [c0000000000a77a8] radix__pudp_huge_get_and_clear+0x28/0x60 Call Trace: [c000000004a2f950] [c000000004a2f9a0] 0xc000000004a2f9a0 (unreliable) [c000000004a2f980] [000d34c100000000] 0xd34c100000000 [c000000004a2f9a0] [c00000000206ba98] pud_advanced_tests+0x118/0x334 [c000000004a2fa40] [c00000000206db34] debug_vm_pgtable+0xcbc/0x1c48 [c000000004a2fc10] [c00000000000fd28] do_one_initcall+0x60/0x388 Also kernel BUG at arch/powerpc/mm/book3s64/pgtable.c:202! .... NIP [c000000000096510] pudp_huge_get_and_clear_full+0x98/0x174 LR [c00000000206bb34] pud_advanced_tests+0x1b4/0x334 Call Trace: [c000000004a2f950] [000d34c100000000] 0xd34c100000000 (unreliable) [c000000004a2f9a0] [c00000000206bb34] pud_advanced_tests+0x1b4/0x334 [c000000004a2fa40] [c00000000206db34] debug_vm_pgtable+0xcbc/0x1c48 [c000000004a2fc10] [c00000000000fd28] do_one_initcall+0x60/0x388

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue appears to affect a narrow debug path, mainly on architectures such as ppc64 when CONFIG_DEBUG_VM is enabled. The described impact is a warning or kernel BUG during debug page-table testing, not a documented remote compromise path.

Executive priority

Treat as a low-urgency stability fix unless your environment runs affected debug-enabled kernels. Include it in normal kernel maintenance, with higher priority for powerpc lab, CI, or specialized production systems.

Technical view

The fix marks PUD advanced-test page-table entries as devmap entries so powerpc debug checks do not reject them. The failure occurs in debug_vm_pgtable during initcall paths, with warnings or BUG_ON traces in radix PUD hugepage update and clear routines.

Likely exposure

Likely limited to Linux systems running affected kernel versions with CONFIG_DEBUG_VM enabled, especially powerpc or similar architectures enforcing these debug checks. Production exposure is unclear from the sources.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, exploit availability, CVSS, or CWE mapping. Evidence points to a correctness and stability failure in kernel debug testing rather than a known attacker-driven exploit path.

Researcher notes

The source data is incomplete on affected version bounds and impact severity. Analysis should focus on CONFIG_DEBUG_VM, debug_vm_pgtable execution, PUD devmap handling, and whether downstream vendors backported the three stable commits.

Mitigation direction

  • Check vendor or distribution advisories for fixed kernel packages.
  • Prioritize affected powerpc systems using CONFIG_DEBUG_VM.
  • Update to a kernel containing the referenced stable fixes.
  • Avoid custom debug kernels in production unless operationally required.

Validation and detection

  • Inventory running kernel versions across Linux fleets.
  • Confirm whether CONFIG_DEBUG_VM is enabled on exposed systems.
  • Check whether systems use powerpc or similar affected architectures.
  • Verify installed kernels include the referenced upstream stable commits.
Prepared
Confidence
medium
Sources
5

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-26850 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
4Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux27af67f35631ac4b61b5e4455b44c9aee8d2cc4b, 27af67f35631ac4b61b5e4455b44c9aee8d2cc4b, 27af67f35631ac4b61b5e4455b44c9aee8d2cc4bunaffected
LinuxLinux6.6, 0, 6.6.21, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

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