CVE-2025-37774

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-13032 (ENISA EUVD) · GHSA-g9q4-8883-7234 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

slab: ensure slab->obj_exts is clear in a newly allocated slab page

ktest recently reported crashes while running several buffered io tests with __alloc_tagging_slab_alloc_hook() at the top of the crash call stack. The signature indicates an invalid address dereference with low bits of slab->obj_exts being set. The bits were outside of the range used by page_memcg_data_flags and objext_flags and hence were not masked out by slab_obj_exts() when obtaining the pointer stored in slab->obj_exts. The typical crash log looks like this:

00510 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 00510 Mem abort info: 00510 ESR = 0x0000000096000045 00510 EC = 0x25: DABT (current EL), IL = 32 bits 00510 SET = 0, FnV = 0 00510 EA = 0, S1PTW = 0 00510 FSC = 0x05: level 1 translation fault 00510 Data abort info: 00510 ISV = 0, ISS = 0x00000045, ISS2 = 0x00000000 00510 CM = 0, WnR = 1, TnD = 0, TagAccess = 0 00510 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 00510 user pgtable: 4k pages, 39-bit VAs, pgdp=0000000104175000 00510 [0000000000000010] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 00510 Internal error: Oops: 0000000096000045 [#1] SMP 00510 Modules linked in: 00510 CPU: 10 UID: 0 PID: 7692 Comm: cat Not tainted 6.15.0-rc1-ktest-g189e17946605 #19327 NONE 00510 Hardware name: linux,dummy-virt (DT) 00510 pstate: 20001005 (nzCv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--) 00510 pc : __alloc_tagging_slab_alloc_hook+0xe0/0x190 00510 lr : __kmalloc_noprof+0x150/0x310 00510 sp : ffffff80c87df6c0 00510 x29: ffffff80c87df6c0 x28: 000000000013d1ff x27: 000000000013d200 00510 x26: ffffff80c87df9e0 x25: 0000000000000000 x24: 0000000000000001 00510 x23: ffffffc08041953c x22: 000000000000004c x21: ffffff80c0002180 00510 x20: fffffffec3120840 x19: ffffff80c4821000 x18: 0000000000000000 00510 x17: fffffffec3d02f00 x16: fffffffec3d02e00 x15: fffffffec3d00700 00510 x14: fffffffec3d00600 x13: 0000000000000200 x12: 0000000000000006 00510 x11: ffffffc080bb86c0 x10: 0000000000000000 x9 : ffffffc080201e58 00510 x8 : ffffff80c4821060 x7 : 0000000000000000 x6 : 0000000055555556 00510 x5 : 0000000000000001 x4 : 0000000000000010 x3 : 0000000000000060 00510 x2 : 0000000000000000 x1 : ffffffc080f50cf8 x0 : ffffff80d801d000 00510 Call trace: 00510 __alloc_tagging_slab_alloc_hook+0xe0/0x190 (P) 00510 __kmalloc_noprof+0x150/0x310 00510 __bch2_folio_create+0x5c/0xf8 00510 bch2_folio_create+0x2c/0x40 00510 bch2_readahead+0xc0/0x460 00510 read_pages+0x7c/0x230 00510 page_cache_ra_order+0x244/0x3a8 00510 page_cache_async_ra+0x124/0x170 00510 filemap_readahead.isra.0+0x58/0xa0 00510 filemap_get_pages+0x454/0x7b0 00510 filemap_read+0xdc/0x418 00510 bch2_read_iter+0x100/0x1b0 00510 vfs_read+0x214/0x300 00510 ksys_read+0x6c/0x108 00510 __arm64_sys_read+0x20/0x30 00510 invoke_syscall.constprop.0+0x54/0xe8 00510 do_el0_svc+0x44/0xc8 00510 el0_svc+0x18/0x58 00510 el0t_64_sync_handler+0x104/0x130 00510 el0t_64_sync+0x154/0x158 00510 Code: d5384100 f9401c01 b9401aa3 b40002e1 (f8227881) 00510 ---[ end trace 0000000000000000 ]--- 00510 Kernel panic - not syncing: Oops: Fatal exception 00510 SMP: stopping secondary CPUs 00510 Kernel Offset: disabled 00510 CPU features: 0x0000,000000e0,00000410,8240500b 00510 Memory Limit: none

Investigation indicates that these bits are already set when we allocate slab page and are not zeroed out after allocation. We are not yet sure why these crashes start happening only recently but regardless of the reason, not initializing a field that gets used later is wrong. Fix it by initializing slab->obj_exts during slab page allocation.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

May 1, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

slab: ensure slab->obj_exts is clear in a newly allocated slab page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2f5819b6ed357c0c350c0616b6b9f38be59adf6
Web page

slab: ensure slab->obj_exts is clear in a newly allocated slab page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28bef6622a1a874fe63aceeb0c684fab75afb3ae
Web page

slab: ensure slab->obj_exts is clear in a newly allocated slab page - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8baa747193591410a853bac9c3710142dfa4937b

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-23ubuntu
linuxKernel @ 6.12.25 (fixes >=6.10.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.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 7× in last 7d / 39× 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 98 of 193 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-37774?
CVE-2025-37774 is a medium-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: slab: ensure slab->obj_exts is clear in a newly allocated slab page ktest recently reported crashes while running several buffered io tests with __alloc_tagging_slab_alloc_hook() at the top of the crash call stack. The signature…
When was the CVE record for CVE-2025-37774 published?
The CVE record for CVE-2025-37774 was published on May 1, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-37774 actively exploited?
CVE-2025-37774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37774?
CVE-2025-37774 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-37774?
A fix for CVE-2025-37774 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-37774?

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

Book a Demo →Browse All CVEs