CVE-2022-49297nbd: fix io hung while disconnecting device
- 5.5MediumCVSS base score
- 0.28%Exploitation in 30 daysEPSS · top 79% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nbd: fix io hung while disconnecting device In our tests, "qemu-nbd" triggers a io hung: INFO: task qemu-nbd:11445 blocked for more than 368 seconds. Not tainted 5.18.0-rc3-next-20220422-00003-g2176915513ca #884 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:qemu-nbd state:D stack: 0 pid:11445 ppid: 1 flags:0x00000000 Call Trace: <TASK> __schedule+0x480/0x1050 ? _raw_spin_lock_irqsave+0x3e/0xb0 schedule+0x9c/0x1b0 blk_mq_freeze_queue_wait+0x9d/0xf0 ? ipi_rseq+0x70/0x70 blk_mq_freeze_queue+0x2b/0x40 nbd_add_socket+0x6b/0x270 [nbd] nbd_ioctl+0x383/0x510 [nbd] blkdev_ioctl+0x18e/0x3e0 __x64_sys_ioctl+0xac/0x120 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fd8ff706577 RSP: 002b:00007fd8fcdfebf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000040000000 RCX: 00007fd8ff706577 RDX: 000000000000000d RSI: 000000000000ab00 RDI: 000000000000000f RBP: 000000000000000f R08: 000000000000fbe8 R09: 000055fe497c62b0 R10: 00000002aff20000 R11: 0000000000000246 R12: 000000000000006d R13: 0000000000000000 R14: 00007ffe82dc5e70 R15: 00007fd8fcdff9c0 "qemu-ndb -d" will call ioctl 'NBD_DISCONNECT' first, however, following message was found: block nbd0: Send disconnect failed -32 Which indicate that something is wrong with the server. Then, "qemu-nbd -d" will call ioctl 'NBD_CLEAR_SOCK', however ioctl can't clear requests after commit 2516ab1543fd("nbd: only clear the queue on device teardown"). And in the meantime, request can't complete through timeout because nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER', which means such request will never be completed in this situation. Now that the flag 'NBD_CMD_INFLIGHT' can make sure requests won't complete multiple times, switch back to call nbd_clear_sock() in nbd_clear_sock_ioctl(), so that inflight requests can be cleared.
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.28% · top 79% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 67e403136a0e1a55fef6a05f103a3979a39ad3fd
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 62d227f67a8c25d5e16f40e5290607f9306d2188
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 69893d6d7f5c10d8306c1b5fc64b71efc91aa6cd
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < f72df77600a43e59b3189e53b47f8685739867d3
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < c4ba982bd5084fa659ef518aaf159e4dab02ecda
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 54b06dc2a206b4d67349bb56b92d4bd32700b7b1
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 141318e62db87105b0103fccc59c9c5940da248d
- affected 2516ab1543fdd1f9d08385d73cae51f668a9f3dc – < 09dadb5985023e27d4740ebd17e6fea4640110e5
- affected 4.12
- unaffected < 4.12
- unaffected 4.14.283 – ≤ 4.14.*
- unaffected 4.19.247 – ≤ 4.19.*
- unaffected 5.4.198 – ≤ 5.4.*
- unaffected 5.10.122 – ≤ 5.10.*
- unaffected 5.15.47 – ≤ 5.15.*
- unaffected 5.17.15 – ≤ 5.17.*
- unaffected 5.18.4 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References
References8
- https://git.kernel.org/stable/c/67e403136a0e1a55fef6a05f103a3979a39ad3fd (opens in a new tab)
- https://git.kernel.org/stable/c/62d227f67a8c25d5e16f40e5290607f9306d2188 (opens in a new tab)
- https://git.kernel.org/stable/c/69893d6d7f5c10d8306c1b5fc64b71efc91aa6cd (opens in a new tab)
- https://git.kernel.org/stable/c/f72df77600a43e59b3189e53b47f8685739867d3 (opens in a new tab)
- https://git.kernel.org/stable/c/c4ba982bd5084fa659ef518aaf159e4dab02ecda (opens in a new tab)
- https://git.kernel.org/stable/c/54b06dc2a206b4d67349bb56b92d4bd32700b7b1 (opens in a new tab)
- https://git.kernel.org/stable/c/141318e62db87105b0103fccc59c9c5940da248d (opens in a new tab)
- https://git.kernel.org/stable/c/09dadb5985023e27d4740ebd17e6fea4640110e5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-54930 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49297)Record last updated .