CVE-2023-52787
published 2024-05-21CVE-2023-52787: In the Linux kernel, the following vulnerability has been resolved: blk-mq: make sure active queue usage is held for bio_integrity_prep()…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
14.5th percentile
In the Linux kernel, the following vulnerability has been resolved:
blk-mq: make sure active queue usage is held for bio_integrity_prep()
blk_integrity_unregister() can come if queue usage counter isn't held
for one bio with integrity prepared, so this request may be completed with
calling profile->complete_fn, then kernel panic.
Another constraint is that bio_integrity_prep() needs to be called
before bio merge.
Fix the issue by:
- call bio_integrity_prep() with one queue usage counter grabbed reliably
- call bio_integrity_prep() before bio merge
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.76-1 (bookworm) | linux 6.1.76-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 900e080752025f0016128f07c9ed4c50eba3654b < b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9 | b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9 |
| linux | linux | >= 900e080752025f0016128f07c9ed4c50eba3654b < e9c309ded295b7f8849097d71ae231456ca79f78 | e9c309ded295b7f8849097d71ae231456ca79f78 |
| linux | linux | >= 900e080752025f0016128f07c9ed4c50eba3654b < b80056bd75a16e4550873ecefe12bc8fd190b1cf | b80056bd75a16e4550873ecefe12bc8fd190b1cf |
| linux | linux | >= 900e080752025f0016128f07c9ed4c50eba3654b < b0077e269f6c152e807fdac90b58caf012cdbaab | b0077e269f6c152e807fdac90b58caf012cdbaab |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.76-1 | 6.1.76-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 5.16 < 6.1.72 | 6.1.72 |
| linux | linux_kernel | >= 6.2 < 6.5.13 | 6.5.13 |
| linux | linux_kernel | >= 6.6 < 6.6.3 | 6.6.3 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-2xv3-4xmw-7ff2: In the Linux kernel, the following vulnerability has been resolved:
blk-mq: make sure active queue usage is held for bio_integrity_prep()
blk_integr
ghsa_unreviewed·2024-05-21
CVE-2023-52787 [MEDIUM] GHSA-2xv3-4xmw-7ff2: In the Linux kernel, the following vulnerability has been resolved:
blk-mq: make sure active queue usage is held for bio_integrity_prep()
blk_integr
In the Linux kernel, the following vulnerability has been resolved:
blk-mq: make sure active queue usage is held for bio_integrity_prep()
blk_integrity_unregister() can come if queue usage counter isn't held
for one bio with integrity prepared, so this request may be completed with
calling profile->complete_fn, then kernel panic.
Another constraint is that bio_integrity_prep() needs to be called
before bio merge.
Fix the issue by:
- call bio_integrity_prep() with one queue usage counter grabbed reliably
- call bio_integrity_prep() before bio merge
OSV
CVE-2023-52787: In the Linux kernel, the following vulnerability has been resolved: blk-mq: make sure active queue usage is held for bio_integrity_prep() blk_integrit
osv·2024-05-21·CVSS 5.5
CVE-2023-52787 [MEDIUM] CVE-2023-52787: In the Linux kernel, the following vulnerability has been resolved: blk-mq: make sure active queue usage is held for bio_integrity_prep() blk_integrit
In the Linux kernel, the following vulnerability has been resolved: blk-mq: make sure active queue usage is held for bio_integrity_prep() blk_integrity_unregister() can come if queue usage counter isn't held for one bio with integrity prepared, so this request may be completed with calling profile->complete_fn, then kernel panic. Another constraint is that bio_integrity_prep() needs to be called before bio merge. Fix the issue by: - call bio_integrity_prep() with one queue usage counter grabbed reliably - call bio_integrity_prep() before bio merge
Red Hat
kernel: blk-mq: make sure active queue usage is held for bio_integrity_prep()
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52787 [MEDIUM] CWE-99 kernel: blk-mq: make sure active queue usage is held for bio_integrity_prep()
kernel: blk-mq: make sure active queue usage is held for bio_integrity_prep()
In the Linux kernel, the following vulnerability has been resolved:
blk-mq: make sure active queue usage is held for bio_integrity_prep()
blk_integrity_unregister() can come if queue usage counter isn't held
for one bio with integrity prepared, so this request may be completed with
calling profile->complete_fn, then kernel panic.
Another constraint is that bio_integrity_prep() needs to be called
before bio merge.
Fix the issue by:
- call bio_integrity_prep() with one queue usage counter grabbed reliably
- call bio_integrity_prep() before bio merge
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterpri
Debian
CVE-2023-52787: linux - In the Linux kernel, the following vulnerability has been resolved: blk-mq: mak...
vendor_debian·2023·CVSS 5.5
CVE-2023-52787 [MEDIUM] CVE-2023-52787: linux - In the Linux kernel, the following vulnerability has been resolved: blk-mq: mak...
In the Linux kernel, the following vulnerability has been resolved: blk-mq: make sure active queue usage is held for bio_integrity_prep() blk_integrity_unregister() can come if queue usage counter isn't held for one bio with integrity prepared, so this request may be completed with calling profile->complete_fn, then kernel panic. Another constraint is that bio_integrity_prep() needs to be called before bio merge. Fix the issue by: - call bio_integrity_prep() with one queue usage counter grabbed reliably - call bio_integrity_prep() before bio merge
Scope: local
bookworm: resolved (fixed in 6.1.76-1)
bullseye: resolved
forky: resolved (fixed in 6.6.8-1)
sid: resolved (fixed in 6.6.8-1)
trixie: resolved (fixed in 6.6.8-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/b0077e269f6c152e807fdac90b58caf012cdbaabhttps://git.kernel.org/stable/c/b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9https://git.kernel.org/stable/c/b80056bd75a16e4550873ecefe12bc8fd190b1cfhttps://git.kernel.org/stable/c/e9c309ded295b7f8849097d71ae231456ca79f78https://git.kernel.org/stable/c/b0077e269f6c152e807fdac90b58caf012cdbaabhttps://git.kernel.org/stable/c/b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9https://git.kernel.org/stable/c/b80056bd75a16e4550873ecefe12bc8fd190b1cfhttps://git.kernel.org/stable/c/e9c309ded295b7f8849097d71ae231456ca79f78
2024-05-21
Published