CVE-2024-53125

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-53125
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).

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/60fd3538d2a8fd44c41d25088c0ece3e1fd30659 Patch
https://git.kernel.org/stable/c/b57ac2d92c1f565743f6890a5b9cf317ed856b09 Patch
https://git.kernel.org/stable/c/bfe9446ea1d95f6cb7848da19dfd58d2eec6fd84 Patch
https://git.kernel.org/stable/c/dadf82c1b2608727bcc306843b540cd7414055a7 Patch
https://git.kernel.org/stable/c/e2ef0f317a52e678fe8fa84b94d6a15b466d6ff0 Patch
https://git.kernel.org/stable/c/e9bd9c498cb0f5843996dbe5cbce7a1836a83c70 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*
History

08 Oct 2025, 15:00

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/60fd3538d2a8fd44c41d25088c0ece3e1fd30659 - () https://git.kernel.org/stable/c/60fd3538d2a8fd44c41d25088c0ece3e1fd30659 - Patch
References () https://git.kernel.org/stable/c/b57ac2d92c1f565743f6890a5b9cf317ed856b09 - () https://git.kernel.org/stable/c/b57ac2d92c1f565743f6890a5b9cf317ed856b09 - Patch
References () https://git.kernel.org/stable/c/bfe9446ea1d95f6cb7848da19dfd58d2eec6fd84 - () https://git.kernel.org/stable/c/bfe9446ea1d95f6cb7848da19dfd58d2eec6fd84 - Patch
References () https://git.kernel.org/stable/c/dadf82c1b2608727bcc306843b540cd7414055a7 - () https://git.kernel.org/stable/c/dadf82c1b2608727bcc306843b540cd7414055a7 - Patch
References () https://git.kernel.org/stable/c/e2ef0f317a52e678fe8fa84b94d6a15b466d6ff0 - () https://git.kernel.org/stable/c/e2ef0f317a52e678fe8fa84b94d6a15b466d6ff0 - Patch
References () https://git.kernel.org/stable/c/e9bd9c498cb0f5843996dbe5cbce7a1836a83c70 - () https://git.kernel.org/stable/c/e9bd9c498cb0f5843996dbe5cbce7a1836a83c70 - Patch
CWE NVD-CWE-noinfo
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
First Time Linux
Linux linux Kernel
CPE cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*

19 Dec 2024, 19:15

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: sync_linked_regs() debe preservar subreg_def La propagación del rango no debe afectar a las marcas subreg_def, de lo contrario el siguiente ejemplo es reescrito incorrectamente por el verificador cuando el indicador BPF_F_TEST_RND_HI32 está establecido: 0: llamar a bpf_ktime_get_ns llamar a bpf_ktime_get_ns 1: r0 &amp;= 0x7fffffff después del verificador r0 &amp;= 0x7fffffff 2: w1 = w0 reescribe w1 = w0 3: si w0 &lt; 10 goto +0 --------------&gt; r11 = 0x2f5674a6 (r) 4: r1 &gt;&gt;= 32 r11 &lt;&lt;= 32 (r) 5: r0 = r1 r1 |= r11 (r) 6: salir; si w0 &lt; 0xa goto pc+0 r1 &gt;&gt;= 32 r0 = r1 salir (o falta la extensión cero de w1 en (2) para arquitecturas que requieren extensión cero para la mitad superior del registro). Lo siguiente ocurre sin este parche: - r0 está marcado como no un subreg en (0); - w1 está marcado como subreg en (2); - el subreg_def de w1 es anulado en (3) por copy_register_state(); - w1 se lee en (5) pero mark_insn_zext() no marca (2) para extensión cero, porque el subreg_def de w1 no está configurado; - debido al indicador BPF_F_TEST_RND_HI32, el verificador inserta un valor aleatorio para los bits hi32 de (2) (marcado (r)); - este valor aleatorio se lee en (5).
References
  • () 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 -

04 Dec 2024, 14:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-12-04 14:15

Updated : 2025-10-08 15:00

NVD link : CVE-2024-53125

Mitre link : CVE-2024-53125

CVE.ORG link : CVE-2024-53125

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo