block: Fix wrong offset in bio_truncate()
Published Jun 20, 2024
7.5
HIGHCVSS 3.1
EPSS 0.92%
Description
bio_truncate() clears the buffer outside of last block of bdev, however current bio_truncate() is using the wrong offset of page. So it can return the uninitialized data.
This happened when both of truncated/corrupted FS and userspace (via bdev) are trying to read the last of bdev.
Affected products
-
- Version 5.4.9StatusaffectedConstraints<5.4.176
- Version
-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version
-
- Version 5.5StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<5.5
- Version 5.10.96StatusunaffectedConstraints<=5.10.*
- Version 5.15.19StatusunaffectedConstraints<=5.15.*
- Version 5.16.5StatusunaffectedConstraints<=5.16.*
- Version 5.17StatusunaffectedConstraints<=*
- Version 5.4.176StatusunaffectedConstraints<=5.4.*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
| ||||||||||||||||||||||||
| Linux | Linux | unaffected |
| ||||||||||||||||||||||||
| Linux | Linux | affected |
|
- < 5.4.176
- ≥ 5.5 · < 5.10.96
- ≥ 5.11 · < 5.15.19
- ≥ 5.16 · < 5.16.5
-
- Version 1da177e4c3f4StatusaffectedConstraints<3ee859e384d4
- Version 1da177e4c3f4StatusaffectedConstraints<4633a79ff8bc
- Version 1da177e4c3f4StatusaffectedConstraints<6cbf4c731d78
- Version 1da177e4c3f4StatusaffectedConstraints<941d5180c430
- Version 1da177e4c3f4StatusaffectedConstraints<b63e120189fd
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux Kernel | n/a |
|
Red Hat Enterprise Linux 8
kernel-0:4.18.0-553.16.1.el8_10
Fixed · RHSA-2024:5101
Red Hat Enterprise Linux 8
kernel-rt-0:4.18.0-553.16.1.rt7.357.el8_10
Fixed · RHSA-2024:5102
Red Hat Enterprise Linux 6
kernel
Not affected
Red Hat Enterprise Linux 7
kernel
Not affected
Red Hat Enterprise Linux 7
kernel-rt
Not affected
Red Hat Enterprise Linux 9
kernel
Not affected
Red Hat Enterprise Linux 9
kernel-rt
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | kernel-0:4.18.0-553.16.1.el8_10 | Fixed | RHSA-2024:5101 |
| Red Hat Enterprise Linux 8 | kernel-rt-0:4.18.0-553.16.1.rt7.357.el8_10 | Fixed | RHSA-2024:5102 |
| Red Hat Enterprise Linux 6 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 7 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
References (10)
- https://access.redhat.com/security/cve/CVE-2022-48747 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2293312 Issue Tracking
- https://git.kernel.org/stable/c/3ee859e384d453d6ac68bfd5971f630d9fa46ad3 Patch
- https://git.kernel.org/stable/c/4633a79ff8bc82770486a063a08b55e5162521d8 Patch
- https://git.kernel.org/stable/c/6cbf4c731d7812518cd857c2cfc3da9fd120f6ae Patch
- https://git.kernel.org/stable/c/941d5180c430ce5b0f7a3622ef9b76077bfa3d82 Patch
- https://git.kernel.org/stable/c/b63e120189fd92aff00096d11e2fc5253f60248b Patch
- https://lore.kernel.org/linux-cve-announce/2024062004-CVE-2022-48747-c63f@gregkh/T
- https://nvd.nist.gov/vuln/detail/CVE-2022-48747
- https://www.cve.org/CVERecord?id=CVE-2022-48747
Change history (0)
No recorded changes yet.