CVE-2022-49190
published 2025-02-26CVE-2022-49190: In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("mem…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
17.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
kernel/resource: fix kfree() of bootmem memory again
Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem
memory"), we could get a resource allocated during boot via
alloc_resource(). And it's required to release the resource using
free_resource(). Howerver, many people use kfree directly which will
result in kernel BUG. In order to fix this without fixing every call
site, just leak a couple of bytes in such corner case.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.17.3-1 (bookworm) | linux 5.17.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= ebff7d8f270d045338d9f4796014f4db429a17f9 < 3379a60f6bb4afcd9c456e340ac525ae649d3ce7 | 3379a60f6bb4afcd9c456e340ac525ae649d3ce7 |
| linux | linux | >= ebff7d8f270d045338d9f4796014f4db429a17f9 < a9e88c2618d228d7a4e7e515cf30dc0d0d813f27 | a9e88c2618d228d7a4e7e515cf30dc0d0d813f27 |
| linux | linux | >= ebff7d8f270d045338d9f4796014f4db429a17f9 < d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8 | d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8 |
| linux | linux | >= ebff7d8f270d045338d9f4796014f4db429a17f9 < ab86020070999e758ce2e60c4348f20bf7ddba56 | ab86020070999e758ce2e60c4348f20bf7ddba56 |
| linux | linux | >= ebff7d8f270d045338d9f4796014f4db429a17f9 < 0cbcc92917c5de80f15c24d033566539ad696892 | 0cbcc92917c5de80f15c24d033566539ad696892 |
| linux | linux_kernel | >= 0 < 5.10.237-1 | 5.10.237-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 3.10 < 5.15.33 | 5.15.33 |
| linux | linux_kernel | >= 5.16 < 5.16.19 | 5.16.19 |
| linux | linux_kernel | >= 5.17 < 5.17.2 | 5.17.2 |
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-h5g4-rrcc-vqf7: In the Linux kernel, the following vulnerability has been resolved:
kernel/resource: fix kfree() of bootmem memory again
Since commit ebff7d8f270d (
ghsa_unreviewed·2025-03-18
CVE-2022-49190 [MEDIUM] CWE-401 GHSA-h5g4-rrcc-vqf7: In the Linux kernel, the following vulnerability has been resolved:
kernel/resource: fix kfree() of bootmem memory again
Since commit ebff7d8f270d (
In the Linux kernel, the following vulnerability has been resolved:
kernel/resource: fix kfree() of bootmem memory again
Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem
memory"), we could get a resource allocated during boot via
alloc_resource(). And it's required to release the resource using
free_resource(). Howerver, many people use kfree directly which will
result in kernel BUG. In order to fix this without fixing every call
site, just leak a couple of bytes in such corner case.
OSV
CVE-2022-49190: In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("m
osv·2025-02-26·CVSS 5.5
CVE-2022-49190 [MEDIUM] CVE-2022-49190: In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("m
In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem memory"), we could get a resource allocated during boot via alloc_resource(). And it's required to release the resource using free_resource(). Howerver, many people use kfree directly which will result in kernel BUG. In order to fix this without fixing every call site, just leak a couple of bytes in such corner case.
Red Hat
kernel: kernel/resource: fix kfree() of bootmem memory again
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49190 [MEDIUM] kernel: kernel/resource: fix kfree() of bootmem memory again
kernel: kernel/resource: fix kfree() of bootmem memory again
In the Linux kernel, the following vulnerability has been resolved:
kernel/resource: fix kfree() of bootmem memory again
Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem
memory"), we could get a resource allocated during boot via
alloc_resource(). And it's required to release the resource using
free_resource(). Howerver, many people use kfree directly which will
result in kernel BUG. In order to fix this without fixing every call
site, just leak a couple of bytes in such corner case.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Ent
Debian
CVE-2022-49190: linux - In the Linux kernel, the following vulnerability has been resolved: kernel/reso...
vendor_debian·2022·CVSS 5.5
CVE-2022-49190 [MEDIUM] CVE-2022-49190: linux - In the Linux kernel, the following vulnerability has been resolved: kernel/reso...
In the Linux kernel, the following vulnerability has been resolved: kernel/resource: fix kfree() of bootmem memory again Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem memory"), we could get a resource allocated during boot via alloc_resource(). And it's required to release the resource using free_resource(). Howerver, many people use kfree directly which will result in kernel BUG. In order to fix this without fixing every call site, just leak a couple of bytes in such corner case.
Scope: local
bookworm: resolved (fixed in 5.17.3-1)
bullseye: resolved (fixed in 5.10.237-1)
forky: resolved (fixed in 5.17.3-1)
sid: resolved (fixed in 5.17.3-1)
trixie: resolved (fixed in 5.17.3-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0cbcc92917c5de80f15c24d033566539ad696892https://git.kernel.org/stable/c/3379a60f6bb4afcd9c456e340ac525ae649d3ce7https://git.kernel.org/stable/c/a9e88c2618d228d7a4e7e515cf30dc0d0d813f27https://git.kernel.org/stable/c/ab86020070999e758ce2e60c4348f20bf7ddba56https://git.kernel.org/stable/c/d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
2025-02-26
Published