CVE-2026-53304

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM 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
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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 PROB
0%
EPSS %ILE
3%
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.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 21× in last 7d / 100× 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 167 total refreshes for this CVE.

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

See which npm, PyPI, Go, and Maven packages are affected by 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