- Vulnerability/
- CVE-2024-53125
CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def
First published: Wed Dec 04 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: bpf: sync_linked_regs() must preserve subreg_def Range propagation must not affect subreg_def marks, otherwise the following example is rewritten by verifier incorrectly when BPF_F_TEST_RND_HI32 flag is set: 0: call bpf_ktime_get_ns call bpf_ktime_get_ns 1: r0 &= 0x7fffffff after verifier r0 &= 0x7fffffff 2: w1 = w0 rewrites w1 = w0 3: if w0 < 10 goto +0 --------------> r11 = 0x2f5674a6 (r) 4: r1 >>= 32 r11 <<= 32 (r) 5: r0 = r1 r1 |= r11 (r) 6: exit; if w0 < 0xa goto pc+0 r1 >>= 32 r0 = r1 exit (or zero extension of w1 at (2) is missing for architectures that require zero extension for upper register half). The following happens w/o this patch: - r0 is marked as not a subreg at (0); - w1 is marked as subreg at (2); - w1 subreg_def is overridden at (3) by copy_register_state(); - w1 is read at (5) but mark_insn_zext() does not mark (2) for zero extension, because w1 subreg_def is not set; - because of BPF_F_TEST_RND_HI32 flag verifier inserts random value for hi32 bits of (2) (marked (r)); - this random value is read at (5).
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
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/e2ef0f317a52e678fe8fa84b94d6a15b466d6ff0
- https://git.kernel.org/stable/c/e9bd9c498cb0f5843996dbe5cbce7a1836a83c70
- https://git.kernel.org/stable/c/60fd3538d2a8fd44c41d25088c0ece3e1fd30659
- https://git.kernel.org/stable/c/b57ac2d92c1f565743f6890a5b9cf317ed856b09
- https://git.kernel.org/stable/c/bfe9446ea1d95f6cb7848da19dfd58d2eec6fd84
- https://git.kernel.org/stable/c/dadf82c1b2608727bcc306843b540cd7414055a7
Frequently Asked Questions
What is the severity of CVE-2024-53125?
CVE-2024-53125 has been classified with a high severity due to its potential impact on system stability and security in the Linux kernel.
How do I fix CVE-2024-53125?
To fix CVE-2024-53125, update your Linux kernel to the latest patched version provided by your Linux distribution.
What versions of the Linux kernel are affected by CVE-2024-53125?
CVE-2024-53125 affects multiple versions of the Linux kernel prior to the patch being released.
What are the potential impacts of CVE-2024-53125?
The potential impacts of CVE-2024-53125 include incorrect behavior in BPF programs which can lead to system crashes or security vulnerabilities.
Who is responsible for addressing CVE-2024-53125?
The responsibility for addressing CVE-2024-53125 lies with the maintainers of the Linux kernel and end-users who must apply the updates.
- agent/title
- agent/type
- agent/severity
- agent/description
- agent/first-publish-date
- agent/author
- agent/event
- collector/nvd-api
- source/NVD
- agent/references
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel