CVE-2026-53304

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

scsi: sg: Resolve soft lockup issue when opening /dev/sgX

The parameter def_reserved_size defines the default buffer size reserved for each Sg_fd and should be restricted to a range between 0 and 1,048,576 (see https://tldp.org/HOWTO/SCSI-Generic-HOWTO/proc.html). Although the function sg_proc_write_dressz enforces this limit, it is possible to bypass it by directly modifying the module parameter as shown below, which then causes a soft lockup:

echo -1 > /sys/module/sg/parameters/def_reserved_size exec 4<> /dev/sg0

watchdog: BUG: soft lockup - CPU#5 stuck for 26 seconds! [bash:537] Modules loaded: CPU: 5 UID: 0 PID: 537 Command: bash, kernel version 6.19.0-rc3+ #134, PREEMPT disabled Hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS version 1.16.1-2.fc37 dated 04/01/2014 ... Call Trace:

sg_build_reserve+0x5c/0xa0 sg_add_sfp+0x168/0x270 sg_open+0x16e/0x340 chrdev_open+0xbe/0x230 do_dentry_open+0x175/0x480 vfs_open+0x34/0xf0 do_open+0x265/0x3d0 path_openat+0x110/0x290 do_filp_open+0xc3/0x170 do_sys_openat2+0x71/0xe0 __x64_sys_openat+0x6d/0xa0 do_syscall_64+0x62/0x310 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The fix is to use module_param_cb to validate and reject invalid values assigned to def_reserved_size.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.1%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (8)

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9676ca7b1ef31a3a65b3e61e7ce3b54ce7364202
generic

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d74e0654ac908c65a8f20373091826fe43b1363
generic

scsi: sg: Resolve soft lockup issue when opening /dev/sgX - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1afd963fcd963db0dc5d47df6dfcf010c9c4647e

Vendor Advisories for CVE-2026-53304(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 60× 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.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:36 UTCVendor advisory
  10. 2026-07-16 17:36 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 18:47 UTCVendor advisory
  13. 2026-07-15 18:46 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 21:01 UTCVendor advisory
  19. 2026-07-14 21:01 UTCGHSA enrichment
  20. 2026-07-13 23:19 UTCGHSA enrichment
  21. 2026-07-13 22:31 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 01:36 UTCVendor advisory
  25. 2026-07-13 01:36 UTCGHSA enrichment
Show 35 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 03:54 UTCVendor advisory
  3. 2026-07-12 03:54 UTCGHSA enrichment
  4. 2026-07-11 06:13 UTCVendor advisory
  5. 2026-07-11 06:13 UTCGHSA enrichment
  6. 2026-07-10 08:28 UTCVendor advisory
  7. 2026-07-10 08:28 UTCGHSA enrichment
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 10:46 UTCGHSA enrichment
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 13:01 UTCEG score recompute▲ 5.50
  14. 2026-07-08 13:01 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 21:35 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-05 15:08 UTCGHSA enrichment
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-02 17:18 UTCGHSA enrichment
  26. 2026-07-01 15:07 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-29 19:28 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-26 21:38 UTCEG score recompute
  35. 2026-06-26 21:37 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53304?
CVE-2026-53304 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Resolve soft lockup issue when opening /dev/sgX The parameter defreservedsize defines the default buffer size reserved for each Sg_fd and should be restricted to a range between 0 and 1,048,576 (see…
When was CVE-2026-53304 disclosed?
CVE-2026-53304 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53304 actively exploited?
CVE-2026-53304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53304?
CVE-2026-53304 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53304?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53304, 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

Explore the affected products and dependency analysis for CVE-2026-53304

Explore →

Is Your Infrastructure Affected by CVE-2026-53304?

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

Start Free Scan →Browse All CVEs