{"vulnerability": "CVE-2024-5012", "sightings": [{"uuid": "7b594eba-b92f-4bfe-ae70-e792faf19e11", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50127", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lska34c7x22r", "content": "", "creation_timestamp": "2025-06-26T22:59:08.044509Z"}, {"uuid": "7a1eb07b-53f5-44f4-a804-18e5217a96fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50125", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lsmfkxk22k2c", "content": "", "creation_timestamp": "2025-06-27T19:42:47.606620Z"}, {"uuid": "d8487cbc-c077-4861-b533-7e050a02327f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50126", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-729/", "content": "", "creation_timestamp": "2025-07-30T03:00:00.000000Z"}, {"uuid": "1fca528c-88cc-46c0-9fc2-9161045e3867", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50125", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6e6867e9-4d3a-49ea-ac10-08d8cad4d90e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50120", "type": "seen", "source": "https://t.me/cvedetector/9924", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50120 - Samba kernel Memory Allocationassi\", \n  \"Content\": \"CVE ID : CVE-2024-50120 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsmb: client: Handle kstrdup failures for passwords  \n  \nIn smb3_reconfigure(), after duplicating ctx->password and  \nctx->password2 with kstrdup(), we need to check for allocation  \nfailures.  \n  \nIf ses->password allocation fails, return -ENOMEM.  \nIf ses->password2 allocation fails, free ses->password, set it  \nto NULL, and return -ENOMEM. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:28.000000Z"}, {"uuid": "b3209cad-9c41-45c0-b333-e2a05c263c12", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50127", "type": "seen", "source": "https://t.me/cvedetector/9932", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50127 - Netgear Linux Kernel Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50127 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: sched: fix use-after-free in taprio_change()  \n  \nIn 'taprio_change()', 'admin' pointer may become dangling due to sched  \nswitch / removal caused by 'advance_sched()', and critical section  \nprotected by 'q->current_entry_lock' is too small to prevent from such  \na scenario (which causes use-after-free detected by KASAN). Fix this  \nby prefer 'rcu_replace_pointer()' over 'rcu_assign_pointer()' to update  \n'admin' immediately before an attempt to schedule freeing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:45:12.000000Z"}, {"uuid": "c75b21eb-9c33-4bfc-992d-b8331f90829e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50129", "type": "seen", "source": "https://t.me/cvedetector/9923", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50129 - Linux Kernel Array Indexing Out-of-Bounds Vulnerability in PSE-PD Driver\", \n  \"Content\": \"CVE ID : CVE-2024-50129 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: pse-pd: Fix out of bound for loop  \n  \nAdjust the loop limit to prevent out-of-bounds access when iterating over  \nPI structures. The loop should not reach the index pcdev->nr_lines since  \nwe allocate exactly pcdev->nr_lines number of PI structures. This fix  \nensures proper bounds are maintained during iterations. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:27.000000Z"}, {"uuid": "a4a48adc-cefc-4436-91b8-795b7155e46a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50128", "type": "seen", "source": "https://t.me/cvedetector/9921", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50128 - Qualcomm Wwan Global Out-of-Bounds Read Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50128 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: wwan: fix global oob in wwan_rtnl_policy  \n  \nThe variable wwan_rtnl_link_ops assign a *bigger* maxtype which leads to  \na global out-of-bounds read when parsing the netlink attributes. Exactly  \nsame bug cause as the oob fixed in commit b33fb5b801c6 (\"net: qualcomm:  \nrmnet: fix global oob in rmnet_policy\").  \n  \n==================================================================  \nBUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:388 [inline]  \nBUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603  \nRead of size 1 at addr ffffffff8b09cb60 by task syz.1.66276/323862  \n  \nCPU: 0 PID: 323862 Comm: syz.1.66276 Not tainted 6.1.70 #1  \nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014  \nCall Trace:  \n   \n __dump_stack lib/dump_stack.c:88 [inline]  \n dump_stack_lvl+0x177/0x231 lib/dump_stack.c:106  \n print_address_description mm/kasan/report.c:284 [inline]  \n print_report+0x14f/0x750 mm/kasan/report.c:395  \n kasan_report+0x139/0x170 mm/kasan/report.c:495  \n validate_nla lib/nlattr.c:388 [inline]  \n __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603  \n __nla_parse+0x3c/0x50 lib/nlattr.c:700  \n nla_parse_nested_deprecated include/net/netlink.h:1269 [inline]  \n __rtnl_newlink net/core/rtnetlink.c:3514 [inline]  \n rtnl_newlink+0x7bc/0x1fd0 net/core/rtnetlink.c:3623  \n rtnetlink_rcv_msg+0x794/0xef0 net/core/rtnetlink.c:6122  \n netlink_rcv_skb+0x1de/0x420 net/netlink/af_netlink.c:2508  \n netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]  \n netlink_unicast+0x74b/0x8c0 net/netlink/af_netlink.c:1352  \n netlink_sendmsg+0x882/0xb90 net/netlink/af_netlink.c:1874  \n sock_sendmsg_nosec net/socket.c:716 [inline]  \n __sock_sendmsg net/socket.c:728 [inline]  \n ____sys_sendmsg+0x5cc/0x8f0 net/socket.c:2499  \n ___sys_sendmsg+0x21c/0x290 net/socket.c:2553  \n __sys_sendmsg net/socket.c:2582 [inline]  \n __do_sys_sendmsg net/socket.c:2591 [inline]  \n __se_sys_sendmsg+0x19e/0x270 net/socket.c:2589  \n do_syscall_x64 arch/x86/entry/common.c:51 [inline]  \n do_syscall_64+0x45/0x90 arch/x86/entry/common.c:81  \n entry_SYSCALL_64_after_hwframe+0x63/0xcd  \nRIP: 0033:0x7f67b19a24ad  \nRSP: 002b:00007f67b17febb8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e  \nRAX: ffffffffffffffda RBX: 00007f67b1b45f80 RCX: 00007f67b19a24ad  \nRDX: 0000000000000000 RSI: 0000000020005e40 RDI: 0000000000000004  \nRBP: 00007f67b1a1e01d R08: 0000000000000000 R09: 0000000000000000  \nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000  \nR13: 00007ffd2513764f R14: 00007ffd251376e0 R15: 00007f67b17fed40  \n   \n  \nThe buggy address belongs to the variable:  \n wwan_rtnl_policy+0x20/0x40  \n  \nThe buggy address belongs to the physical page:  \npage:ffffea00002c2700 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xb09c  \nflags: 0xfff00000001000(reserved|node=0|zone=1|lastcpupid=0x7ff)  \nraw: 00fff00000001000 ffffea00002c2708 ffffea00002c2708 0000000000000000  \nraw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000  \npage dumped because: kasan: bad access detected  \npage_owner info is not present (never set?)  \n  \nMemory state around the buggy address:  \n ffffffff8b09ca00: 05 f9 f9 f9 05 f9 f9 f9 00 01 f9 f9 00 01 f9 f9  \n ffffffff8b09ca80: 00 00 00 05 f9 f9 f9 f9 00 00 03 f9 f9 f9 f9 f9  \n>ffffffff8b09cb00: 00 00 00 00 05 f9 f9 f9 00 00 00 00 f9 f9 f9 f9  \n                                                       ^  \n ffffffff8b09cb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  \n==================================================================  \n  \nAccording to the comment of `nla_parse_nested_deprecated`, use correct size  \n`IFLA_WWAN_MAX` here to fix this issue. \nSeverity: 0.0 | NA \nVisit the link for more de[...]", "creation_timestamp": "2024-11-05T19:44:22.000000Z"}, {"uuid": "549f6348-5bd9-4dbd-94b4-19c09c32162f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50121", "type": "seen", "source": "https://t.me/cvedetector/9930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50121 - Linux NFSd Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50121 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net  \n  \nIn the normal case, when we excute `echo 0 > /proc/fs/nfsd/threads`, the  \nfunction `nfs4_state_destroy_net` in `nfs4_state_shutdown_net` will  \nrelease all resources related to the hashed `nfs4_client`. If the  \n`nfsd_client_shrinker` is running concurrently, the `expire_client`  \nfunction will first unhash this client and then destroy it. This can  \nlead to the following warning. Additionally, numerous use-after-free  \nerrors may occur as well.  \n  \nnfsd_client_shrinker         echo 0 > /proc/fs/nfsd/threads  \n  \nexpire_client                nfsd_shutdown_net  \n  unhash_client                ...  \n                               nfs4_state_shutdown_net  \n                                 /* won't wait shrinker exit */  \n  /*                             cancel_work(&nn->nfsd_shrinker_work)  \n   * nfsd_file for this          /* won't destroy unhashed client1 */  \n   * client1 still alive         nfs4_state_destroy_net  \n   */  \n  \n                               nfsd_file_cache_shutdown  \n                                 /* trigger warning */  \n                                 kmem_cache_destroy(nfsd_file_slab)  \n                                 kmem_cache_destroy(nfsd_file_mark_slab)  \n  /* release nfsd_file and mark */  \n  __destroy_client  \n  \n====================================================================  \nBUG nfsd_file (Not tainted): Objects remaining in nfsd_file on  \n__kmem_cache_shutdown()  \n--------------------------------------------------------------------  \nCPU: 4 UID: 0 PID: 764 Comm: sh Not tainted 6.12.0-rc3+ #1  \n  \n dump_stack_lvl+0x53/0x70  \n slab_err+0xb0/0xf0  \n __kmem_cache_shutdown+0x15c/0x310  \n kmem_cache_destroy+0x66/0x160  \n nfsd_file_cache_shutdown+0xac/0x210 [nfsd]  \n nfsd_destroy_serv+0x251/0x2a0 [nfsd]  \n nfsd_svc+0x125/0x1e0 [nfsd]  \n write_threads+0x16a/0x2a0 [nfsd]  \n nfsctl_transaction_write+0x74/0xa0 [nfsd]  \n vfs_write+0x1a5/0x6d0  \n ksys_write+0xc1/0x160  \n do_syscall_64+0x5f/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \n====================================================================  \nBUG nfsd_file_mark (Tainted: G    B   W         ): Objects remaining  \nnfsd_file_mark on __kmem_cache_shutdown()  \n--------------------------------------------------------------------  \n  \n dump_stack_lvl+0x53/0x70  \n slab_err+0xb0/0xf0  \n __kmem_cache_shutdown+0x15c/0x310  \n kmem_cache_destroy+0x66/0x160  \n nfsd_file_cache_shutdown+0xc8/0x210 [nfsd]  \n nfsd_destroy_serv+0x251/0x2a0 [nfsd]  \n nfsd_svc+0x125/0x1e0 [nfsd]  \n write_threads+0x16a/0x2a0 [nfsd]  \n nfsctl_transaction_write+0x74/0xa0 [nfsd]  \n vfs_write+0x1a5/0x6d0  \n ksys_write+0xc1/0x160  \n do_syscall_64+0x5f/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \nTo resolve this issue, cancel `nfsd_shrinker_work` using synchronous  \nmode in nfs4_state_shutdown_net. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:35.000000Z"}, {"uuid": "7f0e586d-201d-4d9d-9c57-7837bc5aa279", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50123", "type": "seen", "source": "https://t.me/cvedetector/9928", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50123 - Linux Kernel BPF Sockmap Out-of-Bounds Read (Information Disclosure)\", \n  \"Content\": \"CVE ID : CVE-2024-50123 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Add the missing BPF_LINK_TYPE invocation for sockmap  \n  \nThere is an out-of-bounds read in bpf_link_show_fdinfo() for the sockmap  \nlink fd. Fix it by adding the missing BPF_LINK_TYPE invocation for  \nsockmap link  \n  \nAlso add comments for bpf_link_type to prevent missing updates in the  \nfuture. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:34.000000Z"}, {"uuid": "496cebd5-020c-4a62-ad92-1f4218b82491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50124", "type": "seen", "source": "https://t.me/cvedetector/9927", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50124 - Linux Bluetooth ISO Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2024-50124 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: ISO: Fix UAF on iso_sock_timeout  \n  \nconn->sk maybe have been unlinked/freed while waiting for iso_conn_lock  \nso this checks if the conn->sk is still valid by checking if it part of  \niso_sk_list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:33.000000Z"}, {"uuid": "3524a530-e8dc-483e-b128-b6df80925a2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50122", "type": "seen", "source": "https://t.me/cvedetector/9925", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50122 - PCIe Linux Kernel Sysfs Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50122 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI: Hold rescan lock while adding devices during host probe  \n  \nSince adding the PCI power control code, we may end up with a race between  \nthe pwrctl platform device rescanning the bus and host controller probe  \nfunctions. The latter need to take the rescan lock when adding devices or  \nwe may end up in an undefined state having two incompletely added devices  \nand hit the following crash when trying to remove the device over sysfs:  \n  \n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000  \n  Internal error: Oops: 0000000096000004 [#1] SMP  \n  Call trace:  \n    __pi_strlen+0x14/0x150  \n    kernfs_find_ns+0x80/0x13c  \n    kernfs_remove_by_name_ns+0x54/0xf0  \n    sysfs_remove_bin_file+0x24/0x34  \n    pci_remove_resource_files+0x3c/0x84  \n    pci_remove_sysfs_dev_files+0x28/0x38  \n    pci_stop_bus_device+0x8c/0xd8  \n    pci_stop_bus_device+0x40/0xd8  \n    pci_stop_and_remove_bus_device_locked+0x28/0x48  \n    remove_store+0x70/0xb0  \n    dev_attr_store+0x20/0x38  \n    sysfs_kf_write+0x58/0x78  \n    kernfs_fop_write_iter+0xe8/0x184  \n    vfs_write+0x2dc/0x308  \n    ksys_write+0x7c/0xec \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:28.000000Z"}, {"uuid": "825d0ea2-fe32-4bbb-a691-558c9e17ffab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50126", "type": "seen", "source": "https://t.me/cvedetector/9920", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50126 - Linux Kernel net sched RCU use-after-free vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50126 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: sched: use RCU read-side critical section in taprio_dump()  \n  \nFix possible use-after-free in 'taprio_dump()' by adding RCU  \nread-side critical section there. Never seen on x86 but  \nfound on a KASAN-enabled arm64 system when investigating  \n:  \n  \n[T15862] BUG: KASAN: slab-use-after-free in taprio_dump+0xa0c/0xbb0  \n[T15862] Read of size 4 at addr ffff0000d4bb88f8 by task repro/15862  \n[T15862]  \n[T15862] CPU: 0 UID: 0 PID: 15862 Comm: repro Not tainted 6.11.0-rc1-00293-gdefaf1a2113a-dirty #2  \n[T15862] Hardware name: QEMU QEMU Virtual Machine, BIOS edk2-20240524-5.fc40 05/24/2024  \n[T15862] Call trace:  \n[T15862]  dump_backtrace+0x20c/0x220  \n[T15862]  show_stack+0x2c/0x40  \n[T15862]  dump_stack_lvl+0xf8/0x174  \n[T15862]  print_report+0x170/0x4d8  \n[T15862]  kasan_report+0xb8/0x1d4  \n[T15862]  __asan_report_load4_noabort+0x20/0x2c  \n[T15862]  taprio_dump+0xa0c/0xbb0  \n[T15862]  tc_fill_qdisc+0x540/0x1020  \n[T15862]  qdisc_notify.isra.0+0x330/0x3a0  \n[T15862]  tc_modify_qdisc+0x7b8/0x1838  \n[T15862]  rtnetlink_rcv_msg+0x3c8/0xc20  \n[T15862]  netlink_rcv_skb+0x1f8/0x3d4  \n[T15862]  rtnetlink_rcv+0x28/0x40  \n[T15862]  netlink_unicast+0x51c/0x790  \n[T15862]  netlink_sendmsg+0x79c/0xc20  \n[T15862]  __sock_sendmsg+0xe0/0x1a0  \n[T15862]  ____sys_sendmsg+0x6c0/0x840  \n[T15862]  ___sys_sendmsg+0x1ac/0x1f0  \n[T15862]  __sys_sendmsg+0x110/0x1d0  \n[T15862]  __arm64_sys_sendmsg+0x74/0xb0  \n[T15862]  invoke_syscall+0x88/0x2e0  \n[T15862]  el0_svc_common.constprop.0+0xe4/0x2a0  \n[T15862]  do_el0_svc+0x44/0x60  \n[T15862]  el0_svc+0x50/0x184  \n[T15862]  el0t_64_sync_handler+0x120/0x12c  \n[T15862]  el0t_64_sync+0x190/0x194  \n[T15862]  \n[T15862] Allocated by task 15857:  \n[T15862]  kasan_save_stack+0x3c/0x70  \n[T15862]  kasan_save_track+0x20/0x3c  \n[T15862]  kasan_save_alloc_info+0x40/0x60  \n[T15862]  __kasan_kmalloc+0xd4/0xe0  \n[T15862]  __kmalloc_cache_noprof+0x194/0x334  \n[T15862]  taprio_change+0x45c/0x2fe0  \n[T15862]  tc_modify_qdisc+0x6a8/0x1838  \n[T15862]  rtnetlink_rcv_msg+0x3c8/0xc20  \n[T15862]  netlink_rcv_skb+0x1f8/0x3d4  \n[T15862]  rtnetlink_rcv+0x28/0x40  \n[T15862]  netlink_unicast+0x51c/0x790  \n[T15862]  netlink_sendmsg+0x79c/0xc20  \n[T15862]  __sock_sendmsg+0xe0/0x1a0  \n[T15862]  ____sys_sendmsg+0x6c0/0x840  \n[T15862]  ___sys_sendmsg+0x1ac/0x1f0  \n[T15862]  __sys_sendmsg+0x110/0x1d0  \n[T15862]  __arm64_sys_sendmsg+0x74/0xb0  \n[T15862]  invoke_syscall+0x88/0x2e0  \n[T15862]  el0_svc_common.constprop.0+0xe4/0x2a0  \n[T15862]  do_el0_svc+0x44/0x60  \n[T15862]  el0_svc+0x50/0x184  \n[T15862]  el0t_64_sync_handler+0x120/0x12c  \n[T15862]  el0t_64_sync+0x190/0x194  \n[T15862]  \n[T15862] Freed by task 6192:  \n[T15862]  kasan_save_stack+0x3c/0x70  \n[T15862]  kasan_save_track+0x20/0x3c  \n[T15862]  kasan_save_free_info+0x4c/0x80  \n[T15862]  poison_slab_object+0x110/0x160  \n[T15862]  __kasan_slab_free+0x3c/0x74  \n[T15862]  kfree+0x134/0x3c0  \n[T15862]  taprio_free_sched_cb+0x18c/0x220  \n[T15862]  rcu_core+0x920/0x1b7c  \n[T15862]  rcu_core_si+0x10/0x1c  \n[T15862]  handle_softirqs+0x2e8/0xd64  \n[T15862]  __do_softirq+0x14/0x20 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:21.000000Z"}, {"uuid": "8b4cbd2f-c806-4c18-9ddd-0aed378fc1b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50125", "type": "seen", "source": "https://t.me/cvedetector/9919", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50125 - Linux Kernel Bluetooth SCO Use After Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50125 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: SCO: Fix UAF on sco_sock_timeout  \n  \nconn->sk maybe have been unlinked/freed while waiting for sco_conn_lock  \nso this checks if the conn->sk is still valid by checking if it part of  \nsco_sk_list. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:20.000000Z"}]}