CVE-2024-50254
published 2024-11-09CVE-2024-50254: In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_destroy()…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.18%
7.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
bpf_iter_bits_destroy() uses "kit->nr_bits ] kmemleak_alloc+0x4b/0x80
[] __kmalloc_node_noprof+0x480/0x5c0
[] __alloc.isra.0+0x89/0xb0
[] alloc_bulk+0x2af/0x720
[] prefill_mem_cache+0x7f/0xb0
[] bpf_mem_alloc_init+0x3e2/0x610
[] bpf_global_ma_init+0x19/0x30
[] do_one_initcall+0xd3/0x3c0
[] kernel_init_freeable+0x66a/0x940
[] kernel_init+0x20/0x160
[] ret_from_fork+0x3c/0x70
[] ret_from_fork_asm+0x1a/0x30
That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.
Fix the issue by setting kit->bit to kit->nr_bits instead of setting
kit->nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In addition, use "!nr_bits || bits >= nr_bits" to
check whether the iteration is complete and still use "nr_bits > 64" to
indicate whether bits are dynamically allocated. The "!nr_bits" check is
necessary because bpf_iter_bits_new() may fail before setting
kit->nr_bits, and this condition will stop the iteration early instead
of accessing the zeroed or freed kit->bits.
Considering the initial value of kit->bits is -1 and the type of
kit->nr_bits is unsigned int, change the type of kit->nr_bits to int.
The potential overflow problem will be handled in the following patch.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.11.7-1 (forky) | linux 6.11.7-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 4665415975b0827e9646cab91c61d02a6b364d59 < 9cee266fafaf79fd465314546f637f9a3c215830 | 9cee266fafaf79fd465314546f637f9a3c215830 |
| linux | linux | >= 4665415975b0827e9646cab91c61d02a6b364d59 < 101ccfbabf4738041273ce64e2b116cf440dea13 | 101ccfbabf4738041273ce64e2b116cf440dea13 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.11.7-1 | 6.11.7-1 |
| linux | linux_kernel | >= 0 < 6.11.7-1 | 6.11.7-1 |
| linux | linux_kernel | >= 0 < 6.11.0-18.18 | 6.11.0-18.18 |
| linux | linux_kernel | >= 6.11 < 6.11.7 | 6.11.7 |
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.5LOW
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.
OSV
linux-oem-6.11 vulnerabilities
osv·2025-02-28
CVE-2025-0927 linux-oem-6.11 vulnerabilities
linux-oem-6.11 vulnerabilities
Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Compute Acceleration Framework;
- ACPI drivers;
-
OSV
linux-aws, linux-azure, linux-gcp, linux-oracle, linux-raspi, linux-realtime vulnerabilities
osv·2025-02-19
linux-aws, linux-azure, linux-gcp, linux-oracle, linux-raspi, linux-realtime vulnerabilities
linux-aws, linux-azure, linux-gcp, linux-oracle, linux-raspi, linux-realtime vulnerabilities
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Compute Acceleration Framework;
- ACPI drivers;
- Drivers core;
- ATA over ethernet (AOE) driver;
- RAM backed block device driver;
- Network block device driver;
- Ublk userspace block driver;
- Compressed RAM block device driver;
- Bluetooth drivers;
- TPM device driver;
- Clock framework a
OSV
linux, linux-lowlatency vulnerabilities
osv·2025-02-19
CVE-2025-0927 linux, linux-lowlatency vulnerabilities
linux, linux-lowlatency vulnerabilities
Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Compute Acceleration Framework;
- ACPI d
GHSA
GHSA-c7cg-c752-q6q2: In the Linux kernel, the following vulnerability has been resolved:
bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
bpf_iter_bits_de
ghsa_unreviewed·2024-11-09
CVE-2024-50254 [MEDIUM] CWE-401 GHSA-c7cg-c752-q6q2: In the Linux kernel, the following vulnerability has been resolved:
bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
bpf_iter_bits_de
In the Linux kernel, the following vulnerability has been resolved:
bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
bpf_iter_bits_destroy() uses "kit->nr_bits ] kmemleak_alloc+0x4b/0x80
[] __kmalloc_node_noprof+0x480/0x5c0
[] __alloc.isra.0+0x89/0xb0
[] alloc_bulk+0x2af/0x720
[] prefill_mem_cache+0x7f/0xb0
[] bpf_mem_alloc_init+0x3e2/0x610
[] bpf_global_ma_init+0x19/0x30
[] do_one_initcall+0xd3/0x3c0
[] kernel_init_freeable+0x66a/0x940
[] kernel_init+0x20/0x160
[] ret_from_fork+0x3c/0x70
[] ret_from_fork_asm+0x1a/0x30
That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.
Fix the issue by setting kit->bit to kit->nr_bits instead of setting
kit->nr_bits to zero when the iteration completes in
bpf_iter_bits_next(). In additi
OSV
CVE-2024-50254: In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_dest
osv·2024-11-09·CVSS 5.5
CVE-2024-50254 [MEDIUM] CVE-2024-50254: In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_dest
In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_destroy() uses "kit->nr_bits ] kmemleak_alloc+0x4b/0x80 [] __kmalloc_node_noprof+0x480/0x5c0 [] __alloc.isra.0+0x89/0xb0 [] alloc_bulk+0x2af/0x720 [] prefill_mem_cache+0x7f/0xb0 [] bpf_mem_alloc_init+0x3e2/0x610 [] bpf_global_ma_init+0x19/0x30 [] do_one_initcall+0xd3/0x3c0 [] kernel_init_freeable+0x66a/0x940 [] kernel_init+0x20/0x160 [] ret_from_fork+0x3c/0x70 [] ret_from_fork_asm+0x1a/0x30 That is because nr_bits will be set as zero in bpf_iter_bits_next() after all bits have been iterated. Fix the issue by setting kit->bit to kit->nr_bits instead of setting kit->nr_bits to zero when the iteration completes in bpf_iter_bits_next(). In addition,
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2025-02-28
CVE-2024-47738 Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
-
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2025-02-19
CVE-2024-47738 Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Compute Acceleration Framework;
- ACPI drivers;
- Drivers core;
- ATA over ethernet (AOE) driver;
- RAM backed block device driver;
- Network block device driver;
- Ublk userspace block driver;
- Compressed RAM block device driver;
- Bluetooth drivers;
- TPM device driver;
- Clock fr
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2025-02-19
CVE-2024-49996 Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM32 architecture;
- ARM64 architecture;
- PowerPC architecture;
- RISC-V architecture;
- S390 architecture;
- SuperH RISC architecture;
- User-Mode Linux (UML);
- x86 architecture;
- Block layer subsystem;
-
Red Hat
kernel: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
vendor_redhat·2024-11-09·CVSS 5.5
CVE-2024-50254 [MEDIUM] CWE-401 kernel: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
kernel: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
In the Linux kernel, the following vulnerability has been resolved:
bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
bpf_iter_bits_destroy() uses "kit->nr_bits ] kmemleak_alloc+0x4b/0x80
[] __kmalloc_node_noprof+0x480/0x5c0
[] __alloc.isra.0+0x89/0xb0
[] alloc_bulk+0x2af/0x720
[] prefill_mem_cache+0x7f/0xb0
[] bpf_mem_alloc_init+0x3e2/0x610
[] bpf_global_ma_init+0x19/0x30
[] do_one_initcall+0xd3/0x3c0
[] kernel_init_freeable+0x66a/0x940
[] kernel_init+0x20/0x160
[] ret_from_fork+0x3c/0x70
[] ret_from_fork_asm+0x1a/0x30
That is because nr_bits will be set as zero in bpf_iter_bits_next()
after all bits have been iterated.
Fix the issue by setting kit->bit to kit->nr_bits instead of setting
kit->nr_bits to
Debian
CVE-2024-50254: linux - In the Linux kernel, the following vulnerability has been resolved: bpf: Free d...
vendor_debian·2024·CVSS 5.5
CVE-2024-50254 [MEDIUM] CVE-2024-50254: linux - In the Linux kernel, the following vulnerability has been resolved: bpf: Free d...
In the Linux kernel, the following vulnerability has been resolved: bpf: Free dynamically allocated bits in bpf_iter_bits_destroy() bpf_iter_bits_destroy() uses "kit->nr_bits ] kmemleak_alloc+0x4b/0x80 [] __kmalloc_node_noprof+0x480/0x5c0 [] __alloc.isra.0+0x89/0xb0 [] alloc_bulk+0x2af/0x720 [] prefill_mem_cache+0x7f/0xb0 [] bpf_mem_alloc_init+0x3e2/0x610 [] bpf_global_ma_init+0x19/0x30 [] do_one_initcall+0xd3/0x3c0 [] kernel_init_freeable+0x66a/0x940 [] kernel_init+0x20/0x160 [] ret_from_fork+0x3c/0x70 [] ret_from_fork_asm+0x1a/0x30 That is because nr_bits will be set as zero in bpf_iter_bits_next() after all bits have been iterated. Fix the issue by setting kit->bit to kit->nr_bits instead of setting kit->nr_bits to zero when the iteration completes in bpf_iter_bits_next(). In addition,
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-11-09
Published