{"vulnerability": "CVE-2024-53125", "sightings": [{"uuid": "10193d8c-2423-4e84-89b1-e8a2a12ef33a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-53125", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113594971054570634", "content": "", "creation_timestamp": "2024-12-04T14:15:02.376376Z"}, {"uuid": "d7010fb9-5828-4e5c-94f4-04317ac1204a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-53125", "type": "seen", "source": "https://t.me/cvedetector/11989", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-53125 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-53125 \nPublished : Dec. 4, 2024, 2:15 p.m. | 31\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: sync_linked_regs() must preserve subreg_def  \n  \nRange propagation must not affect subreg_def marks, otherwise the  \nfollowing example is rewritten by verifier incorrectly when  \nBPF_F_TEST_RND_HI32 flag is set:  \n  \n  0: call bpf_ktime_get_ns                   call bpf_ktime_get_ns  \n  1: r0 &amp;= 0x7fffffff       after verifier   r0 &amp;= 0x7fffffff  \n  2: w1 = w0                rewrites         w1 = w0  \n  3: if w0 &lt; 10 goto +0     --------------&gt;  r11 = 0x2f5674a6     (r)  \n  4: r1 &gt;&gt;= 32                               r11 &lt;=&gt;= 32  \n                                             r0 = r1  \n                                             exit  \n  \n(or zero extension of w1 at (2) is missing for architectures that  \n require zero extension for upper register half).  \n  \nThe following happens w/o this patch:  \n- r0 is marked as not a subreg at (0);  \n- w1 is marked as subreg at (2);  \n- w1 subreg_def is overridden at (3) by copy_register_state();  \n- w1 is read at (5) but mark_insn_zext() does not mark (2)  \n  for zero extension, because w1 subreg_def is not set;  \n- because of BPF_F_TEST_RND_HI32 flag verifier inserts random  \n  value for hi32 bits of (2) (marked (r));  \n- this random value is read at (5). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-04T15:55:03.000000Z"}]}