Medium 5.5Published Jun 26, 2026

CVE-2026-53304scsi: sg: Resolve soft lockup issue when opening /dev/sgX

Updated under an hour ago (Oct 26, 2026, 11:40 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Jun 26, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	6460e75a104d10458817d2f5b2fbff775bf0b43a builds before 3d74e0654ac908c65a8f20373091826fe43b1363; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before c47ccfb3d80dfed522ca06a5954ac97488d78c5a; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before fe671d3c84ffb1b763d590c25195755adeaadaba; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before c5f4a211e82d04ccc1809311322c47023bbe66e2; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before 9676ca7b1ef31a3a65b3e61e7ce3b54ce7364202; 6460e75a104d10458817d2f5b2fbff775bf0b43a builds before 1afd963fcd963db0dc5d47df6dfcf010c9c4647e; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before feade299e932967de27519338d41de348fb5b061; from 6460e75a104d10458817d2f5b2fbff775bf0b43a before d06a310b45e153872033dd0cf19d5a2279121099	CNA record
linux linux_kernel linux:linux_kernel	from 2.6.19 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.141; from 6.7 before 6.12.91; from 6.13 before 6.18.33; from 6.19 before 7.0.10	NVD

References

References

https://git.kernel.org/stable/c/3d74e0654ac908c65a8f20373091826fe43b1363	patch
https://git.kernel.org/stable/c/c47ccfb3d80dfed522ca06a5954ac97488d78c5a	patch
https://git.kernel.org/stable/c/fe671d3c84ffb1b763d590c25195755adeaadaba	patch
https://git.kernel.org/stable/c/c5f4a211e82d04ccc1809311322c47023bbe66e2	patch
https://git.kernel.org/stable/c/9676ca7b1ef31a3a65b3e61e7ce3b54ce7364202	patch
https://git.kernel.org/stable/c/1afd963fcd963db0dc5d47df6dfcf010c9c4647e	patch
https://git.kernel.org/stable/c/feade299e932967de27519338d41de348fb5b061	patch
https://git.kernel.org/stable/c/d06a310b45e153872033dd0cf19d5a2279121099	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.