CVE-2024-47723: jfs: fix out-of-bounds in dbNextAG() and diAlloc()
First published: Mon Oct 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=2.6.12<5.10.227 | |
| Linux Kernel | >=5.11<5.15.168 | |
| Linux Kernel | >=5.16<6.1.113 | |
| Linux Kernel | >=6.2<6.6.54 | |
| Linux Kernel | >=6.7<6.10.13 | |
| Linux Kernel | >=6.11<6.11.2 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/0338e66cba272351ca9d7d03f3628e390e70963b
- https://git.kernel.org/stable/c/128d5cfdcf844cb690c9295a3a1c1114c21fc15a
- https://git.kernel.org/stable/c/5ad6284c8d433f8a213111c5c44ead4d9705b622
- https://git.kernel.org/stable/c/6ce8b6ab44a8b5918c0ee373d4ad19d19017931b
- https://git.kernel.org/stable/c/96855f40e152989c9e7c20c4691ace5581098acc
- https://git.kernel.org/stable/c/c1ba4b8ca799ff1d99d01f37d7ccb7d5ba5533d2
- https://git.kernel.org/stable/c/d1017d2a0f3f16dc1db5120e7ddbe7c6680425b0
- https://git.kernel.org/stable/c/e63866a475562810500ea7f784099bfe341e761a
- https://git.kernel.org/stable/c/ead82533278502428883085a787d5a00f15e5eb9
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47723
- https://nvd.nist.gov/vuln/detail/CVE-2024-47723
- https://launchpad.net/bugs/cve/CVE-2024-47723
- https://security-tracker.debian.org/tracker/CVE-2024-47723
- https://ubuntu.com/security/CVE-2024-47723
- https://git.kernel.org/linus/e63866a475562810500ea7f784099bfe341e761a
Frequently Asked Questions
What is the severity of CVE-2024-47723?
CVE-2024-47723 has been classified with a medium severity level due to its potential for causing out-of-bounds access.
How do I fix CVE-2024-47723?
To resolve CVE-2024-47723, it is recommended to update the Linux kernel to versions that include the patch, such as 6.1.123-1 or 6.12.12-1.
Which versions of the Linux kernel are affected by CVE-2024-47723?
CVE-2024-47723 affects multiple versions of the Linux kernel ranging from 2.6.12 to 6.11.2.
What is the impact of CVE-2024-47723?
The impact of CVE-2024-47723 can lead to potential crashes or unexpected behaviors in systems using the affected versions of the Linux kernel.
Is there a workaround for CVE-2024-47723?
There may not be any effective workarounds besides applying the necessary kernel updates to mitigate CVE-2024-47723.
- agent/title
- agent/type
- agent/first-publish-date
- agent/remedy
- agent/weakness
- agent/severity
- agent/author
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/tags
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/2.6.12
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.11
- package-manager/debian