CVE-2026-23383

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing

struct bpf_plt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT buffer.

Because the base address of the JIT buffer can be 4-byte aligned (e.g., ending in 0x4 or 0xc), the relative padding logic in build_plt() fails to ensure that target lands on an 8-byte boundary.

This leads to two issues:

  • UBSAN reports misaligned-access warnings when dereferencing the
structure.
  • More critically, target is updated concurrently via WRITE_ONCE() in
bpf_arch_text_poke() while the JIT'd code executes ldr. On arm64, 64-bit loads/stores are only guaranteed to be single-copy atomic if they are 64-bit aligned. A misaligned target risks a torn read, causing the JIT to jump to a corrupted address.

Fix this by increasing the allocation alignment requirement to 8 bytes (sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of the JIT buffer to an 8-byte boundary, allowing the relative padding math in build_plt() to correctly align the target field.

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

March 25, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80ad264da02cc4aee718e799c2b79f0f834673dc
generic

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66959ed481a474eaae278c7f6860a2a9b188a4d6
generic

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/519b1ad91de5bf7a496f2b858e9212db6328e1de

Vendor Advisories for CVE-2026-23383(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.77osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (120 versions)6.19.8-1

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 4× in last 7d / 23× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23383?
CVE-2026-23383 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpf_plt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT buffer. Because the…
When was CVE-2026-23383 disclosed?
CVE-2026-23383 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23383 actively exploited?
CVE-2026-23383 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23383?
CVE-2026-23383 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23383?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23383, 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-23383

Explore →

Is Your Infrastructure Affected by CVE-2026-23383?

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