CVE-2025-38279

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-07-10. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

bpf: Do not include stack ptr register in precision backtracking bookkeeping

Yi Lai reported an issue ([1]) where the following warning appears in kernel dmesg: [ 60.643604] verifier backtracking bug [ 60.643635] WARNING: CPU: 10 PID: 2315 at kernel/bpf/verifier.c:4302 __mark_chain_precision+0x3a6c/0x3e10 [ 60.648428] Modules linked in: bpf_testmod(OE) [ 60.650471] CPU: 10 UID: 0 PID: 2315 Comm: test_progs Tainted: G OE 6.15.0-rc4-gef11287f8289-dirty #327 PREEMPT(full) [ 60.654385] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 60.656682] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 60.660475] RIP: 0010:__mark_chain_precision+0x3a6c/0x3e10 [ 60.662814] Code: 5a 30 84 89 ea e8 c4 d9 01 00 80 3d 3e 7d d8 04 00 0f 85 60 fa ff ff c6 05 31 7d d8 04 01 48 c7 c7 00 58 30 84 e8 c4 06 a5 ff <0f> 0b e9 46 fa ff ff 48 ... [ 60.668720] RSP: 0018:ffff888116cc7298 EFLAGS: 00010246 [ 60.671075] RAX: 54d70e82dfd31900 RBX: ffff888115b65e20 RCX: 0000000000000000 [ 60.673659] RDX: 0000000000000001 RSI: 0000000000000004 RDI: 00000000ffffffff [ 60.676241] RBP: 0000000000000400 R08: ffff8881f6f23bd3 R09: 1ffff1103ede477a [ 60.678787] R10: dffffc0000000000 R11: ffffed103ede477b R12: ffff888115b60ae8 [ 60.681420] R13: 1ffff11022b6cbc4 R14: 00000000fffffff2 R15: 0000000000000001 [ 60.684030] FS: 00007fc2aedd80c0(0000) GS:ffff88826fa8a000(0000) knlGS:0000000000000000 [ 60.686837] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 60.689027] CR2: 000056325369e000 CR3: 000000011088b002 CR4: 0000000000370ef0 [ 60.691623] Call Trace: [ 60.692821] [ 60.693960] ? __pfx_verbose+0x10/0x10 [ 60.695656] ? __pfx_disasm_kfunc_name+0x10/0x10 [ 60.697495] check_cond_jmp_op+0x16f7/0x39b0 [ 60.699237] do_check+0x58fa/0xab10 ...

Further analysis shows the warning is at line 4302 as below:

4294 /* static subprog call instruction, which 4295 * means that we are exiting current subprog, 4296 * so only r1-r5 could be still requested as 4297 * precise, r0 and r6-r10 or any stack slot in 4298 * the current frame should be zero by now 4299 */ 4300 if (bt_reg_mask(bt) & ~BPF_REGMASK_ARGS) { 4301 verbose(env, "BUG regs %x\n", bt_reg_mask(bt)); 4302 WARN_ONCE(1, "verifier backtracking bug"); 4303 return -EFAULT; 4304 }

With the below test (also in the next patch): __used __naked static void __bpf_jmp_r10(void) { asm volatile ( "r2 = 2314885393468386424 ll;" "goto +0;" "if r2 <= r10 goto +3;" "if r1 >= -1835016 goto +0;" "if r2 <= 8 goto +0;" "if r3 <= 0 goto +0;" "exit;" ::: __clobber_all); }

SEC("?raw_tp") __naked void bpf_jmp_r10(void) { asm volatile ( "r3 = 0 ll;" "call __bpf_jmp_r10;" "r0 = 0;" "exit;" ::: __clobber_all); }

The following is the verifier failure log: 0: (18) r3 = 0x0 ; R3_w=0 2: (85) call pc+2 caller: R10=fp0 callee: frame1: R1=ctx() R3_w=0 R10=fp0 5: frame1: R1=ctx() R3_w=0 R10=fp0 ; asm volatile (" \ @ verifier_precision.c:184 5: (18) r2 = 0x20202000256c6c78 ; frame1: R2_w=0x20202000256c6c78 7: (05) goto pc+0 8: (bd) if r2 <= r10 goto pc+3 ; frame1: R2_w=0x20202000256c6c78 R10=fp0 9: (35) if r1 >= 0xffe3fff8 goto pc+0 ; frame1: R1=ctx() 10: (b5) if r2 <= 0x8 goto pc+0 mark_precise: frame1: last_idx 10 first_idx 0 subseq_idx -1 mark_precise: frame1: regs=r2 stack= before 9: (35) if r1 >= 0xffe3fff8 goto pc+0 mark_precise: frame1: regs=r2 stack= before 8: (bd) if r2 <= r10 goto pc+3 mark_preci ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 10, 2025

Last Modified

March 17, 2026

References (3)

Vendor Advisories for CVE-2025-38279(3)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1012.12) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1012.12) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
linuxKernel @ 6.12.37 (fixes >=6.5.0)—osv

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 rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—

Additional Vendor Advisories

(23)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 152 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 64 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-12 17:07 UTCEG score recompute
  4. 2026-10-11 20:40 UTCEG score recompute
  5. 2026-10-11 18:51 UTCEG score recompute
  6. 2026-10-11 15:28 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-02 09:11 UTCOSV refresh
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 63 more
  1. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-09-13 07:24 UTCOSV refresh
  6. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-08-25 07:57 UTCOSV refresh
  23. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-08-09 01:50 UTCOSV refresh
  34. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-07-24 01:11 UTCOSV refresh
  49. 2026-07-23 02:54 UTCEG score recompute
  50. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  59. 2026-07-13 22:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  60. 2026-07-13 06:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-07-12 05:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-07-11 08:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  63. 2026-07-09 19:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-38279?
CVE-2025-38279 is a high-severity vulnerability; its CVE record was published on July 10, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf: Do not include stack ptr register in precision backtracking bookkeeping Yi Lai reported an issue ([1]) where the following warning appears in kernel dmesg: [ 60.643604] verifier backtracking bug [ 60.643635] WARNING: CPU: 10…
When was the CVE record for CVE-2025-38279 published?
The CVE record for CVE-2025-38279 was published on July 10, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of March 17, 2026; the record at its source may have been updated since.
Is CVE-2025-38279 actively exploited?
CVE-2025-38279 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38279?
CVE-2025-38279 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38279?
A fix for CVE-2025-38279 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38279 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38279

Explore →

Is Your Infrastructure Affected by CVE-2025-38279?

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

Book a Demo →Browse All CVEs