CVE-2026-46279

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

mm/alloc_tag: clear codetag for pages allocated before page_ext initialization

Due to initialization ordering, page_ext is allocated and initialized relatively late during boot. Some pages have already been allocated and freed before page_ext becomes available, leaving their codetag uninitialized.

A clear example is in init_section_page_ext(): alloc_page_ext() calls kmemleak_alloc(). If the slab cache has no free objects, it falls back to the buddy allocator to allocate memory. However, at this point page_ext is not yet fully initialized, so these newly allocated pages have no codetag set. These pages may later be reclaimed by KASAN, which causes the warning to trigger when they are freed because their codetag ref is still empty.

Use a global array to track pages allocated before page_ext is fully initialized. The array size is fixed at 8192 entries, and will emit a warning if this limit is exceeded. When page_ext initialization completes, set their codetag to empty to avoid warnings when they are freed later.

This warning is only observed with CONFIG_MEM_ALLOC_PROFILING_DEBUG=Y and mem_profiling_compressed disabled:

[ 9.582133] ------------[ cut here ]------------ [ 9.582137] alloc_tag was not set [ 9.582139] WARNING: ./include/linux/alloc_tag.h:164 at __pgalloc_tag_sub+0x40f/0x550, CPU#5: systemd/1 [ 9.582190] CPU: 5 UID: 0 PID: 1 Comm: systemd Not tainted 7.0.0-rc4 #1 PREEMPT(lazy) [ 9.582192] Hardware name: Red Hat KVM, BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 9.582194] RIP: 0010:__pgalloc_tag_sub+0x40f/0x550 [ 9.582196] Code: 00 00 4c 29 e5 48 8b 05 1f 88 56 05 48 8d 4c ad 00 48 8d 2c c8 e9 87 fd ff ff 0f 0b 0f 0b e9 f3 fe ff ff 48 8d 3d 61 2f ed 03 <67> 48 0f b9 3a e9 b3 fd ff ff 0f 0b eb e4 e8 5e cd 14 02 4c 89 c7 [ 9.582197] RSP: 0018:ffffc9000001f940 EFLAGS: 00010246 [ 9.582200] RAX: dffffc0000000000 RBX: 1ffff92000003f2b RCX: 1ffff110200d806c [ 9.582201] RDX: ffff8881006c0360 RSI: 0000000000000004 RDI: ffffffff9bc7b460 [ 9.582202] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff3a62324 [ 9.582203] R10: ffffffff9d311923 R11: 0000000000000000 R12: ffffea0004001b00 [ 9.582204] R13: 0000000000002000 R14: ffffea0000000000 R15: ffff8881006c0360 [ 9.582206] FS: 00007ffbbcf2d940(0000) GS:ffff888450479000(0000) knlGS:0000000000000000 [ 9.582208] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9.582210] CR2: 000055ee3aa260d0 CR3: 0000000148b67005 CR4: 0000000000770ef0 [ 9.582211] PKRU: 55555554 [ 9.582212] Call Trace: [ 9.582213] [ 9.582214] ? __pfx___pgalloc_tag_sub+0x10/0x10 [ 9.582216] ? check_bytes_and_report+0x68/0x140 [ 9.582219] __free_frozen_pages+0x2e4/0x1150 [ 9.582221] ? __free_slab+0xc2/0x2b0 [ 9.582224] qlist_free_all+0x4c/0xf0 [ 9.582227] kasan_quarantine_reduce+0x15d/0x180 [ 9.582229] __kasan_slab_alloc+0x69/0x90 [ 9.582232] kmem_cache_alloc_noprof+0x14a/0x500 [ 9.582234] do_getname+0x96/0x310 [ 9.582237] do_readlinkat+0x91/0x2f0 [ 9.582239] ? __pfx_do_readlinkat+0x10/0x10 [ 9.582240] ? get_random_bytes_user+0x1df/0x2c0 [ 9.582244] __x64_sys_readlinkat+0x96/0x100 [ 9.582246] do_syscall_64+0xce/0x650 [ 9.582250] ? __x64_sys_getrandom+0x13a/0x1e0 [ 9.582252] ? __pfx___x64_sys_getrandom+0x10/0x10 [ 9.582254] ? do_syscall_64+0x114/0x650 [ 9.582255] ? ksys_read+0xfc/0x1d0 [ 9.582258] ? __pfx_ksys_read+0x10/0x10 [ 9.582260] ? do_syscall_64+0x114/0x650 [ 9.582262] ? do_syscall_64+0x114/0x650 [ 9.582264] ? __pfx_fput_close_sync+0x10/0x10 [ 9.582266] ? file_close_fd_locked+0x178/0x2a0 [ 9.582268] ? __x64_sys_faccessat2+0x96/0x100 [ 9.582269] ? __x64_sys_close+0x7d/0xd0 [ 9.582271] ? do_syscall_64+0x114/0x650 [ 9.582273] ? do_syscall_64+0x114/0x650 [ 9.582275] ? clear_bhb_loop+0x50/0xa0 [ 9.582277] ? clear_bhb_l ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 8, 2026

Last Modified

July 8, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

mm/alloc_tag: clear codetag for pages allocated before page_ext initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5b495ba9de0423ef39f8bd86729a885870c7efe
generic

mm/alloc_tag: clear codetag for pages allocated before page_ext initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b49dfabc38cad5e50af24f63edd124a10de3ebb6
generic

mm/alloc_tag: clear codetag for pages allocated before page_ext initialization - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b1842775a460245e97d36d3a67d0cfba7c4ff79

Vendor Advisories for CVE-2026-46279(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 24× in last 7d / 120× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 214 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 01:24 UTCEG score recompute
  4. 2026-08-25 01:24 UTCVendor advisory
  5. 2026-08-25 01:24 UTCGHSA enrichment
  6. 2026-08-24 00:51 UTCVendor advisory
  7. 2026-08-24 00:51 UTCGHSA enrichment
  8. 2026-08-23 11:51 UTCEG score recompute
  9. 2026-08-23 11:51 UTCVendor advisory
  10. 2026-08-23 11:51 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 01:42 UTCEG score recompute
  13. 2026-08-22 01:42 UTCVendor advisory
  14. 2026-08-22 01:42 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 12:42 UTCEG score recompute
  17. 2026-08-21 12:42 UTCVendor advisory
  18. 2026-08-21 12:42 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 22:30 UTCVendor advisory
  21. 2026-08-20 22:30 UTCGHSA enrichment
  22. 2026-08-20 09:30 UTCEG score recompute
  23. 2026-08-20 09:30 UTCVendor advisory
  24. 2026-08-20 09:30 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 03:26 UTCVendor advisory
  4. 2026-08-17 03:26 UTCGHSA enrichment
  5. 2026-08-16 14:26 UTCEG score recompute
  6. 2026-08-16 14:26 UTCVendor advisory
  7. 2026-08-16 14:26 UTCGHSA enrichment
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-16 01:14 UTCVendor advisory
  10. 2026-08-16 01:14 UTCGHSA enrichment
  11. 2026-08-15 11:59 UTCEG score recompute
  12. 2026-08-15 11:59 UTCVendor advisory
  13. 2026-08-15 11:59 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 17:04 UTCVendor advisory
  16. 2026-08-14 17:04 UTCGHSA enrichment
  17. 2026-08-14 04:04 UTCEG score recompute
  18. 2026-08-14 04:04 UTCVendor advisory
  19. 2026-08-14 04:04 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 15:04 UTCVendor advisory
  22. 2026-08-13 15:04 UTCGHSA enrichment
  23. 2026-08-13 02:00 UTCEG score recompute
  24. 2026-08-13 02:00 UTCVendor advisory
  25. 2026-08-13 02:00 UTCGHSA enrichment
  26. 2026-08-12 13:51 UTCEPSS rescore
  27. 2026-08-12 13:00 UTCVendor advisory
  28. 2026-08-12 13:00 UTCGHSA enrichment
  29. 2026-08-11 23:22 UTCEG score recompute
  30. 2026-08-11 23:22 UTCVendor advisory
  31. 2026-08-11 23:22 UTCGHSA enrichment
  32. 2026-08-11 10:22 UTCEG score recompute
  33. 2026-08-11 10:22 UTCVendor advisory
  34. 2026-08-11 10:22 UTCGHSA enrichment
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 21:23 UTCVendor advisory
  37. 2026-08-10 21:23 UTCGHSA enrichment
  38. 2026-08-10 05:31 UTCVendor advisory
  39. 2026-08-10 05:31 UTCGHSA enrichment
  40. 2026-08-09 16:31 UTCVendor advisory
  41. 2026-08-09 16:31 UTCGHSA enrichment
  42. 2026-08-09 03:32 UTCEG score recompute
  43. 2026-08-09 03:32 UTCVendor advisory
  44. 2026-08-09 03:32 UTCGHSA enrichment
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 14:32 UTCVendor advisory
  47. 2026-08-08 14:32 UTCGHSA enrichment
  48. 2026-08-08 01:32 UTCVendor advisory
  49. 2026-08-08 01:32 UTCGHSA enrichment
  50. 2026-08-07 12:32 UTCVendor advisory
  51. 2026-08-07 12:32 UTCGHSA enrichment
  52. 2026-08-06 23:33 UTCEG score recompute
  53. 2026-08-06 23:33 UTCVendor advisory
  54. 2026-08-06 23:33 UTCGHSA enrichment
  55. 2026-08-06 13:47 UTCEPSS rescore
  56. 2026-08-06 09:16 UTCVendor advisory
  57. 2026-08-06 09:16 UTCGHSA enrichment
  58. 2026-08-05 20:16 UTCEG score recompute
  59. 2026-08-05 20:16 UTCVendor advisory
  60. 2026-08-05 20:16 UTCGHSA enrichment
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-04 17:21 UTCEG score recompute
  63. 2026-08-04 17:21 UTCVendor advisory
  64. 2026-08-04 17:21 UTCGHSA enrichment
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-04 04:21 UTCVendor advisory
  68. 2026-08-04 04:21 UTCGHSA enrichment
  69. 2026-08-03 15:21 UTCEG score recompute
  70. 2026-08-03 15:21 UTCVendor advisory
  71. 2026-08-03 15:21 UTCGHSA enrichment
  72. 2026-08-03 10:36 UTCEPSS rescore
  73. 2026-08-03 01:49 UTCVendor advisory
  74. 2026-08-03 01:49 UTCGHSA enrichment
  75. 2026-08-02 12:50 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46279?
CVE-2026-46279 is a high vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/alloctag: clear codetag for pages allocated before pageext initialization Due to initialization ordering, page_ext is allocated and initialized relatively late during boot. Some pages have already been allocated and freed before…
When was CVE-2026-46279 disclosed?
CVE-2026-46279 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46279 actively exploited?
CVE-2026-46279 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-46279?
CVE-2026-46279 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46279?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46279, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46279

Explore →

Is Your Infrastructure Affected by CVE-2026-46279?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs