admin/nvd-json-data-feeds
1
0 Fork 0
mirror of https://github.com/fkie-cad/nvd-json-data-feeds.git synced 2026-10-29 01:10:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto-Update: 2025-09-17T16:00:11.938210+00:00

Browse Source
This commit is contained in:
cad-safe-bot committed 2025-09-17 16:03:55 +00:00
1 parent 58c969c811
commit 5a2f9fb50e
340 files changed
+10528 -1379
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

CVE-2009/CVE-2009-200xx/CVE-2009-20005.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2009-20005",
"sourceIdentifier": "[email protected]",
"published": "2025-09-16T15:15:41.780",
"lastModified": "2025-09-16T19:15:33.543",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2009/CVE-2009-200xx/CVE-2009-20006.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2009-20006",
"sourceIdentifier": "[email protected]",
"published": "2025-09-16T15:15:41.953",
"lastModified": "2025-09-16T19:15:33.870",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2009/CVE-2009-200xx/CVE-2009-20007.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2009-20007",
"sourceIdentifier": "[email protected]",
"published": "2025-09-16T15:15:42.113",
"lastModified": "2025-09-16T19:15:34.017",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [
{
"sourceIdentifier": "[email protected]",
CVE-2022/CVE-2022-430xx/CVE-2022-43021.json
+5 -1
View File
@@ -2,7 +2,7 @@
"id": "CVE-2022-43021",
"sourceIdentifier": "[email protected]",
"published": "2022-10-19T18:15:13.880",
"lastModified": "2025-05-09T15:15:56.230",
"lastModified": "2025-09-17T14:15:34.260",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -99,6 +99,10 @@
}
],
"references": [
{
"url": "https://github.com/hansmach1ne/CVE-portfolio/tree/main/CVE-2022-43021",
"source": "[email protected]"
},
{
"url": "https://github.com/hansmach1ne/opencats_zero-days/blob/main/SQLI_JobOrders.md",
"source": "[email protected]",
CVE-2022/CVE-2022-430xx/CVE-2022-43022.json
+5 -1
View File
@@ -2,7 +2,7 @@
"id": "CVE-2022-43022",
"sourceIdentifier": "[email protected]",
"published": "2022-10-19T18:15:13.943",
"lastModified": "2025-05-09T15:15:56.417",
"lastModified": "2025-09-17T14:15:35.310",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -99,6 +99,10 @@
}
],
"references": [
{
"url": "https://github.com/hansmach1ne/CVE-portfolio/tree/main/CVE-2022-43022",
"source": "[email protected]"
},
{
"url": "https://github.com/hansmach1ne/opencats_zero-days/blob/main/SQLI_tag_deletion.md",
"source": "[email protected]",
CVE-2022/CVE-2022-430xx/CVE-2022-43023.json
+5 -1
View File
@@ -2,7 +2,7 @@
"id": "CVE-2022-43023",
"sourceIdentifier": "[email protected]",
"published": "2022-10-19T18:15:14.007",
"lastModified": "2025-05-09T15:15:56.600",
"lastModified": "2025-09-17T14:15:35.470",
"vulnStatus": "Modified",
"cveTags": [],
"descriptions": [
@@ -99,6 +99,10 @@
}
],
"references": [
{
"url": "https://github.com/hansmach1ne/CVE-portfolio/tree/main/CVE-2022-43023",
"source": "[email protected]"
},
{
"url": "https://github.com/hansmach1ne/opencats_zero-days/blob/main/SQLI_imports_errors.md",
"source": "[email protected]",
CVE-2022/CVE-2022-503xx/CVE-2022-50339.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50339",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:32.647",
"lastModified": "2025-09-16T17:15:32.647",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50340.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50340",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:33.533",
"lastModified": "2025-09-16T17:15:33.533",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50341.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50341",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:33.660",
"lastModified": "2025-09-16T17:15:33.660",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50342.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50342",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:33.807",
"lastModified": "2025-09-16T17:15:33.807",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50343.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50343",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:33.923",
"lastModified": "2025-09-16T17:15:33.923",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50344.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50344",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.070",
"lastModified": "2025-09-16T17:15:34.070",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50345.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50345",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.203",
"lastModified": "2025-09-16T17:15:34.203",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50346.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50346",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.330",
"lastModified": "2025-09-16T17:15:34.330",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50347.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50347",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.470",
"lastModified": "2025-09-16T17:15:34.470",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50348.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50348",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.590",
"lastModified": "2025-09-16T17:15:34.590",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50349.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50349",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.703",
"lastModified": "2025-09-16T17:15:34.703",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50350.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50350",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.833",
"lastModified": "2025-09-16T17:15:34.833",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50351.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50351",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:34.980",
"lastModified": "2025-09-16T17:15:34.980",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50352.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2022-50352",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:35.080",
"lastModified": "2025-09-16T17:15:35.080",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2022/CVE-2022-503xx/CVE-2022-50353.json
+49
View File
@@ -0,0 +1,49 @@
{
"id": "CVE-2022-50353",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:33.270",
"lastModified": "2025-09-17T15:15:33.270",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: wmt-sdmmc: fix return value check of mmc_add_host()\n\nmmc_add_host() may return error, if we ignore its return value, the memory\nthat allocated in mmc_alloc_host() will be leaked and it will lead a kernel\ncrash because of deleting not added device in the remove path.\n\nSo fix this by checking the return value and goto error path which will call\nmmc_free_host(), besides, clk_disable_unprepare() also needs be called."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/29276d56f6ed138db0f38cd31aedc0b725c8c76c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/58c3a8d0f1abeb1ca5c2df948be58ad4f7bb6f67",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/70b0620afab3c69d95a7e2dd7ceff162a21c4009",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9bedf64dda84b29151e41591d8ded9ff0e6d336a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b40ac3b696a9c84b36211ef0c3f5a422650c101b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c7a328cea791cc2769b6417943939420913b4a46",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/eb7a2d516d4fbd165c07877a20feccb047342b1f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ecd6f77af3478f5223aa4011642a891b7dc91228",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50354.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2022-50354",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.037",
"lastModified": "2025-09-17T15:15:34.037",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: Fix kfd_process_device_init_vm error handling\n\nShould only destroy the ib_mem and let process cleanup worker to free\nthe outstanding BOs. Reset the pointer in pdd->qpd structure, to avoid\nNULL pointer access in process destroy worker.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000010\n Call Trace:\n amdgpu_amdkfd_gpuvm_unmap_gtt_bo_from_kernel+0x46/0xb0 [amdgpu]\n kfd_process_device_destroy_cwsr_dgpu+0x40/0x70 [amdgpu]\n kfd_process_destroy_pdds+0x71/0x190 [amdgpu]\n kfd_process_wq_release+0x2a2/0x3b0 [amdgpu]\n process_one_work+0x2a1/0x600\n worker_thread+0x39/0x3d0"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/29d48b87db64b6697ddad007548e51d032081c59",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9d74d1f52e16d8e07f7fbe52e96d6391418a2fe9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b6e78bd3bf2eb964c95eb2596d3cd367307a20b5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50355.json
+45
View File
@@ -0,0 +1,45 @@
{
"id": "CVE-2022-50355",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.150",
"lastModified": "2025-09-17T15:15:34.150",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: vt6655: fix some erroneous memory clean-up loops\n\nIn some initialization functions of this driver, memory is allocated with\n'i' acting as an index variable and increasing from 0. The commit in\n\"Fixes\" introduces some clean-up codes in case of allocation failure,\nwhich free memory in reverse order with 'i' decreasing to 0. However,\nthere are some problems:\n - The case i=0 is left out. Thus memory is leaked.\n - In case memory allocation fails right from the start, the memory\n freeing loops will start with i=-1 and invalid memory locations will\n be accessed.\n\nOne of these loops has been fixed in commit c8ff91535880 (\"staging:\nvt6655: fix potential memory leak\"). Fix the remaining erroneous loops."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2a2db520e3ca5aafba7c211abfd397666c9b5f9d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/637672a71f5016a40b0a6c0f3c8ad25eacedc8c3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/95ac62e8545be2b0a8cae0beef7c682e2e470e48",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a9e9806d1c315bc50dce05479a079b9a104474b8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ed11b73c963292e7b49c0f37025c58ed3b7921d6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f19e5b7df54590c831f350381963f25585c8f7d5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50356.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2022-50356",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.277",
"lastModified": "2025-09-17T15:15:34.277",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: sfb: fix null pointer access issue when sfb_init() fails\n\nWhen the default qdisc is sfb, if the qdisc of dev_queue fails to be\ninited during mqprio_init(), sfb_reset() is invoked to clear resources.\nIn this case, the q->qdisc is NULL, and it will cause gpf issue.\n\nThe process is as follows:\nqdisc_create_dflt()\n\tsfb_init()\n\t\ttcf_block_get() --->failed, q->qdisc is NULL\n\t...\n\tqdisc_put()\n\t\t...\n\t\tsfb_reset()\n\t\t\tqdisc_reset(q->qdisc) --->q->qdisc is NULL\n\t\t\t\tops = qdisc->ops\n\nThe following is the Call Trace information:\ngeneral protection fault, probably for non-canonical address\n0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN\nKASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]\nRIP: 0010:qdisc_reset+0x2b/0x6f0\nCall Trace:\n<TASK>\nsfb_reset+0x37/0xd0\nqdisc_reset+0xed/0x6f0\nqdisc_destroy+0x82/0x4c0\nqdisc_put+0x9e/0xb0\nqdisc_create_dflt+0x2c3/0x4a0\nmqprio_init+0xa71/0x1760\nqdisc_create+0x3eb/0x1000\ntc_modify_qdisc+0x408/0x1720\nrtnetlink_rcv_msg+0x38e/0xac0\nnetlink_rcv_skb+0x12d/0x3a0\nnetlink_unicast+0x4a2/0x740\nnetlink_sendmsg+0x826/0xcc0\nsock_sendmsg+0xc5/0x100\n____sys_sendmsg+0x583/0x690\n___sys_sendmsg+0xe8/0x160\n__sys_sendmsg+0xbf/0x160\ndo_syscall_64+0x35/0x80\nentry_SYSCALL_64_after_hwframe+0x46/0xb0\nRIP: 0033:0x7f2164122d04\n</TASK>"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2a3fc78210b9f0e85372a2435368962009f480fc",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/723399af2795fb95687a531c9480464b5f489333",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c2e1e59d59fafe297779ceae1fe0e6fbebc3e745",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ded86c4191a3c17f8200d17a7d8a6f63b74554ae",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50357.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2022-50357",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.397",
"lastModified": "2025-09-17T15:15:34.397",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: core: fix some leaks in probe\n\nThe dwc3_get_properties() function calls:\n\n\tdwc->usb_psy = power_supply_get_by_name(usb_psy_name);\n\nso there is some additional clean up required on these error paths."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2a735e4b5580a2a6bbd6572109b4c4f163c57462",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3a213503f483173e7eea76f2e7e3bdd6df7fd6f8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/79c3afb55942368921237d7b5355d48c52bdde20",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50358.json
+41
View File
@@ -0,0 +1,41 @@
{
"id": "CVE-2022-50358",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.510",
"lastModified": "2025-09-17T15:15:34.510",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbrcmfmac: return error when getting invalid max_flowrings from dongle\n\nWhen firmware hit trap at initialization, host will read abnormal\nmax_flowrings number from dongle, and it will cause kernel panic when\ndoing iowrite to initialize dongle ring.\nTo detect this error at early stage, we directly return error when getting\ninvalid max_flowrings(>256)."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/10c4b63d09a5b0ebf1b61af1dae7f25555cf58b6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/200347eb3b2608cc8b54c13dd1d5e03809ba2eb2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2aca4f3734bd717e04943ddf340d49ab62299a00",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2e8bb402b060a6c22160de3d72cee057698177c8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3cc9299036bdb647408e11e41de3eb1ff6d428cd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/87f126b25fa8562196f0f4c0aa46a446026199bf",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50359.json
+53
View File
@@ -0,0 +1,53 @@
{
"id": "CVE-2022-50359",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.633",
"lastModified": "2025-09-17T15:15:34.633",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: cx88: Fix a null-ptr-deref bug in buffer_prepare()\n\nWhen the driver calls cx88_risc_buffer() to prepare the buffer, the\nfunction call may fail, resulting in a empty buffer and null-ptr-deref\nlater in buffer_queue().\n\nThe following log can reveal it:\n\n[ 41.822762] general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI\n[ 41.824488] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n[ 41.828027] RIP: 0010:buffer_queue+0xc2/0x500\n[ 41.836311] Call Trace:\n[ 41.836945] __enqueue_in_driver+0x141/0x360\n[ 41.837262] vb2_start_streaming+0x62/0x4a0\n[ 41.838216] vb2_core_streamon+0x1da/0x2c0\n[ 41.838516] __vb2_init_fileio+0x981/0xbc0\n[ 41.839141] __vb2_perform_fileio+0xbf9/0x1120\n[ 41.840072] vb2_fop_read+0x20e/0x400\n[ 41.840346] v4l2_read+0x215/0x290\n[ 41.840603] vfs_read+0x162/0x4c0\n\nFix this by checking the return value of cx88_risc_buffer()\n\n[hverkuil: fix coding style issues]"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/10c99d1c46ea9cd940029e17bab11d021f315c21",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2b064d91440b33fba5b452f2d1b31f13ae911d71",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4befc7ffa18ef9a4b70d854465313a345a06862f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/644d5a87ab1863eb606526ea743021752a17e9cb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6f21976095c1e92454ab030976f95f40d652351b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/704838040f3bdb4aa07ff4f26505a666a3defcfe",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9181af2dbf06e7f432e5dbe88d10b22343e851b9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c2257c8a501537afab276c306cb717b7260276e1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c76d04d2079a4b7369ce9a0e859c0f3f2250bcc1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50360.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2022-50360",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.753",
"lastModified": "2025-09-17T15:15:34.753",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dp: fix aux-bus EP lifetime\n\nDevice-managed resources allocated post component bind must be tied to\nthe lifetime of the aggregate DRM device or they will not necessarily be\nreleased when binding of the aggregate device is deferred.\n\nThis can lead resource leaks or failure to bind the aggregate device\nwhen binding is later retried and a second attempt to allocate the\nresources is made.\n\nFor the DP aux-bus, an attempt to populate the bus a second time will\nsimply fail (\"DP AUX EP device already populated\").\n\nFix this by tying the lifetime of the EP device to the DRM device rather\nthan DP controller platform device.\n\nPatchwork: https://patchwork.freedesktop.org/patch/502672/"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2b57f726611e294dc4297dd48eb8c98ef1938e82",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8768663188e4169333f66583e4d2432e65c421df",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50361.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2022-50361",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.867",
"lastModified": "2025-09-17T15:15:34.867",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: add missing unregister_netdev() in wilc_netdev_ifc_init()\n\nFault injection test reports this issue:\n\nkernel BUG at net/core/dev.c:10731!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\nCall Trace:\n <TASK>\n wilc_netdev_ifc_init+0x19f/0x220 [wilc1000 884bf126e9e98af6a708f266a8dffd53f99e4bf5]\n wilc_cfg80211_init+0x30c/0x380 [wilc1000 884bf126e9e98af6a708f266a8dffd53f99e4bf5]\n wilc_bus_probe+0xad/0x2b0 [wilc1000_spi 1520a7539b6589cc6cde2ae826a523a33f8bacff]\n spi_probe+0xe4/0x140\n really_probe+0x17e/0x3f0\n __driver_probe_device+0xe3/0x170\n driver_probe_device+0x49/0x120\n\nThe root case here is alloc_ordered_workqueue() fails, but\ncfg80211_unregister_netdevice() or unregister_netdev() not be called in\nerror handling path. To fix add unregister_netdev goto lable to add the\nunregister operation in error handling path."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2b88974ecb358990e1c33fabcd0b9e142bab7f21",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6da6ce086221803ed6c3b1db11096cecd3e58ec8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a1bdecedc7ad0512365267cd1a26bfc2ae455c59",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50362.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2022-50362",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:34.980",
"lastModified": "2025-09-17T15:15:34.980",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: hisilicon: Add multi-thread support for a DMA channel\n\nWhen we get a DMA channel and try to use it in multiple threads it\nwill cause oops and hanging the system.\n\n% echo 100 > /sys/module/dmatest/parameters/threads_per_chan\n% echo 100 > /sys/module/dmatest/parameters/iterations\n% echo 1 > /sys/module/dmatest/parameters/run\n[383493.327077] Unable to handle kernel paging request at virtual\n\t\taddress dead000000000108\n[383493.335103] Mem abort info:\n[383493.335103] ESR = 0x96000044\n[383493.335105] EC = 0x25: DABT (current EL), IL = 32 bits\n[383493.335107] SET = 0, FnV = 0\n[383493.335108] EA = 0, S1PTW = 0\n[383493.335109] FSC = 0x04: level 0 translation fault\n[383493.335110] Data abort info:\n[383493.335111] ISV = 0, ISS = 0x00000044\n[383493.364739] CM = 0, WnR = 1\n[383493.367793] [dead000000000108] address between user and kernel\n\t\taddress ranges\n[383493.375021] Internal error: Oops: 96000044 [#1] PREEMPT SMP\n[383493.437574] CPU: 63 PID: 27895 Comm: dma0chan0-copy2 Kdump:\n\t\tloaded Tainted: GO 5.17.0-rc4+ #2\n[383493.457851] pstate: 204000c9 (nzCv daIF +PAN -UAO -TCO -DIT\n\t\t-SSBS BTYPE=--)\n[383493.465331] pc : vchan_tx_submit+0x64/0xa0\n[383493.469957] lr : vchan_tx_submit+0x34/0xa0\n\nThis occurs because the transmission timed out, and that's due\nto data race. Each thread rewrite channels's descriptor as soon as\ndevice_issue_pending is called. It leads to the situation that\nthe driver thinks that it uses the right descriptor in interrupt\nhandler while channels's descriptor has been changed by other\nthread. The descriptor which in fact reported interrupt will not\nbe handled any more, as well as its tx->callback.\nThat's why timeout reports.\n\nWith current fixes channels' descriptor changes it's value only\nwhen it has been used. A new descriptor is acquired from\nvc->desc_issued queue that is already filled with descriptors\nthat are ready to be sent. Threads have no direct access to DMA\nchannel descriptor. In case of channel's descriptor is busy, try\nto submit to HW again when a descriptor is completed. In this case,\nvc->desc_issued may be empty when hisi_dma_start_transfer is called,\nso delete error reporting on this. Now it is just possible to queue\na descriptor for further processing."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2cbb95883c990d0002a77e13d3278913ab26ad79",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7cb9b20941e1fb20d22d0a2f460a3d4fa417274c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/af12e209a9d559394d35875ba0e6c80407605888",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d4a8ec5cc7ff5d442bd49a44f26d74b2021ba4c8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f4cee0b385cd0348e071d4d80c4c13cfe547c70d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50363.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2022-50363",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.107",
"lastModified": "2025-09-17T15:15:35.107",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskmsg: pass gfp argument to alloc_sk_msg()\n\nsyzbot found that alloc_sk_msg() could be called from a\nnon sleepable context. sk_psock_verdict_recv() uses\nrcu_read_lock() protection.\n\nWe need the callers to pass a gfp_t argument to avoid issues.\n\nsyzbot report was:\n\nBUG: sleeping function called from invalid context at include/linux/sched/mm.h:274\nin_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 3613, name: syz-executor414\npreempt_count: 0, expected: 0\nRCU nest depth: 1, expected: 0\nINFO: lockdep is turned off.\nCPU: 0 PID: 3613 Comm: syz-executor414 Not tainted 6.0.0-syzkaller-09589-g55be6084c8e0 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022\nCall Trace:\n<TASK>\n__dump_stack lib/dump_stack.c:88 [inline]\ndump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106\n__might_resched+0x538/0x6a0 kernel/sched/core.c:9877\nmight_alloc include/linux/sched/mm.h:274 [inline]\nslab_pre_alloc_hook mm/slab.h:700 [inline]\nslab_alloc_node mm/slub.c:3162 [inline]\nslab_alloc mm/slub.c:3256 [inline]\nkmem_cache_alloc_trace+0x59/0x310 mm/slub.c:3287\nkmalloc include/linux/slab.h:600 [inline]\nkzalloc include/linux/slab.h:733 [inline]\nalloc_sk_msg net/core/skmsg.c:507 [inline]\nsk_psock_skb_ingress_self+0x5c/0x330 net/core/skmsg.c:600\nsk_psock_verdict_apply+0x395/0x440 net/core/skmsg.c:1014\nsk_psock_verdict_recv+0x34d/0x560 net/core/skmsg.c:1201\ntcp_read_skb+0x4a1/0x790 net/ipv4/tcp.c:1770\ntcp_rcv_established+0x129d/0x1a10 net/ipv4/tcp_input.c:5971\ntcp_v4_do_rcv+0x479/0xac0 net/ipv4/tcp_ipv4.c:1681\nsk_backlog_rcv include/net/sock.h:1109 [inline]\n__release_sock+0x1d8/0x4c0 net/core/sock.c:2906\nrelease_sock+0x5d/0x1c0 net/core/sock.c:3462\ntcp_sendmsg+0x36/0x40 net/ipv4/tcp.c:1483\nsock_sendmsg_nosec net/socket.c:714 [inline]\nsock_sendmsg net/socket.c:734 [inline]\n__sys_sendto+0x46d/0x5f0 net/socket.c:2117\n__do_sys_sendto net/socket.c:2129 [inline]\n__se_sys_sendto net/socket.c:2125 [inline]\n__x64_sys_sendto+0xda/0xf0 net/socket.c:2125\ndo_syscall_x64 arch/x86/entry/common.c:50 [inline]\ndo_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80\nentry_SYSCALL_64_after_hwframe+0x63/0xcd"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d1f274b95c6e4ba6a813b3b8e7a1a38d54a0a08",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/693ddd6ffc05b228ea1638f9d757c5d3541f9446",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50364.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2022-50364",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.227",
"lastModified": "2025-09-17T15:15:35.227",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: mux: reg: check return value after calling platform_get_resource()\n\nIt will cause null-ptr-deref in resource_size(), if platform_get_resource()\nreturns NULL, move calling resource_size() after devm_ioremap_resource() that\nwill check 'res' to avoid null-ptr-deref.\nAnd use devm_platform_get_and_ioremap_resource() to simplify code."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d47b79d2bd39cc6369eccf94a06568d84c906ae",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/61df25c41b8e0d2c988ccf17139f70075a2e1ba4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8212800943997fab61874550278d653cb378c60c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f5049b3ad9446203b916ee375f30fa217735f63a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f7a440c89b6d460154efeb058272760e41bdfea8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50365.json
+53
View File
@@ -0,0 +1,53 @@
{
"id": "CVE-2022-50365",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.343",
"lastModified": "2025-09-17T15:15:35.343",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskbuff: Account for tail adjustment during pull operations\n\nExtending the tail can have some unexpected side effects if a program uses\na helper like BPF_FUNC_skb_pull_data to read partial content beyond the\nhead skb headlen when all the skbs in the gso frag_list are linear with no\nhead_frag -\n\n kernel BUG at net/core/skbuff.c:4219!\n pc : skb_segment+0xcf4/0xd2c\n lr : skb_segment+0x63c/0xd2c\n Call trace:\n skb_segment+0xcf4/0xd2c\n __udp_gso_segment+0xa4/0x544\n udp4_ufo_fragment+0x184/0x1c0\n inet_gso_segment+0x16c/0x3a4\n skb_mac_gso_segment+0xd4/0x1b0\n __skb_gso_segment+0xcc/0x12c\n udp_rcv_segment+0x54/0x16c\n udp_queue_rcv_skb+0x78/0x144\n udp_unicast_rcv_skb+0x8c/0xa4\n __udp4_lib_rcv+0x490/0x68c\n udp_rcv+0x20/0x30\n ip_protocol_deliver_rcu+0x1b0/0x33c\n ip_local_deliver+0xd8/0x1f0\n ip_rcv+0x98/0x1a4\n deliver_ptype_list_skb+0x98/0x1ec\n __netif_receive_skb_core+0x978/0xc60\n\nFix this by marking these skbs as GSO_DODGY so segmentation can handle\nthe tail updates accordingly."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d59f0ca153e9573ec4f140988c0ccca0eb4181b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2d7afdcbc9d32423f177ee12b7c93783aea338fb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/331615d837f4979eb91a336a223a5c7f7886ecd5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/668dc454bcbd1da73605201ff43f988c70848215",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6ac417d71b80e74b002313fcd73f7e9008e8e457",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/821be5a5ab09a40ba09cb5ba354f18cf7996fea0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8fb773eed4909ef5dc1bbeb3629a337d3336df7e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/946dd5dc4fcc4123cdfe3942b20012c4448cf89a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ff3743d00f41d803e6ab9334962b674f3b7fd0cb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50366.json
+53
View File
@@ -0,0 +1,53 @@
{
"id": "CVE-2022-50366",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.467",
"lastModified": "2025-09-17T15:15:35.467",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\npowercap: intel_rapl: fix UBSAN shift-out-of-bounds issue\n\nWhen value < time_unit, the parameter of ilog2() will be zero and\nthe return value is -1. u64(-1) is too large for shift exponent\nand then will trigger shift-out-of-bounds:\n\nshift exponent 18446744073709551615 is too large for 32-bit type 'int'\nCall Trace:\n rapl_compute_time_window_core\n rapl_write_data_raw\n set_time_window\n store_constraint_time_window_us"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/139bbbd01114433b80fe59f5e1330615aadf9752",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/1d94af37565e4d3c26b0d63428e093a37d5b4c32",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2d93540014387d1c73b9ccc4d7895320df66d01b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3eb0ba70376f6ee40fa843fc9cee49269370b0b3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/42f79dbb9514f726ff21df25f09cb0693b0b2445",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/49a6ffdaed60f0eb52c198fafebc05994e16e305",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4ebba43384722adbd325baec3a12c572d94488eb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6216b685b8f48ab7b721a6fd5acbf526b41c13e8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/708b9abe1b4a2f050a483db4b7edfc446b13df1f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50367.json
+53
View File
@@ -0,0 +1,53 @@
{
"id": "CVE-2022-50367",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.590",
"lastModified": "2025-09-17T15:15:35.590",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs: fix UAF/GPF bug in nilfs_mdt_destroy\n\nIn alloc_inode, inode_init_always() could return -ENOMEM if\nsecurity_inode_alloc() fails, which causes inode->i_private\nuninitialized. Then nilfs_is_metadata_file_inode() returns\ntrue and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(),\nwhich frees the uninitialized inode->i_private\nand leads to crashes(e.g., UAF/GPF).\n\nFix this by moving security_inode_alloc just prior to\nthis_cpu_inc(nr_inodes)"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1e555c3ed1fce4b278aaebe18a64a934cece57d8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2e488f13755ffbb60f307e991b27024716a33b29",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/64b79e632869ad3ef6c098a4731d559381da1115",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/70e4f70d54e0225f91814e8610477d65f33cefe4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/81de80330fa6907aec32eb54c5619059e6e36452",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d1ff475d7c83289d0a7faef346ea3bbf90818bad",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50368.json
+41
View File
@@ -0,0 +1,41 @@
{
"id": "CVE-2022-50368",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.717",
"lastModified": "2025-09-17T15:15:35.717",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dsi: fix memory corruption with too many bridges\n\nAdd the missing sanity check on the bridge counter to avoid corrupting\ndata beyond the fixed-sized bridge array in case there are ever more\nthan eight bridges.\n\nPatchwork: https://patchwork.freedesktop.org/patch/502668/"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/21c4679af01f1027cb559330c2e7d410089b2b36",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2e786eb2f9cebb07e317226b60054df510b60c65",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4e5587cddb334f7a5bb1c49ea8bbfc966fafe1b8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9f035d1fb30648fe70ee01627eb131c56d699b35",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e83b354890a3c1d5256162f87a6cc38c47ae7f20",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f649ed0e1b7a1545f8e27267d3c468b3cb222ece",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50369.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2022-50369",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.830",
"lastModified": "2025-09-17T15:15:35.830",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vkms: Fix null-ptr-deref in vkms_release()\n\nA null-ptr-deref is triggered when it tries to destroy the workqueue in\nvkms->output.composer_workq in vkms_release().\n\n KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\n CPU: 5 PID: 17193 Comm: modprobe Not tainted 6.0.0-11331-gd465bff130bf #24\n RIP: 0010:destroy_workqueue+0x2f/0x710\n ...\n Call Trace:\n <TASK>\n ? vkms_config_debugfs_init+0x50/0x50 [vkms]\n __devm_drm_dev_alloc+0x15a/0x1c0 [drm]\n vkms_init+0x245/0x1000 [vkms]\n do_one_initcall+0xd0/0x4f0\n do_init_module+0x1a4/0x680\n load_module+0x6249/0x7110\n __do_sys_finit_module+0x140/0x200\n do_syscall_64+0x35/0x80\n entry_SYSCALL_64_after_hwframe+0x46/0xb0\n\nThe reason is that an OOM happened which triggers the destroy of the\nworkqueue, however, the workqueue is alloced in the later process,\nthus a null-ptr-deref happened. A simple call graph is shown as below:\n\n vkms_init()\n vkms_create()\n devm_drm_dev_alloc()\n __devm_drm_dev_alloc()\n devm_drm_dev_init()\n devm_add_action_or_reset()\n devm_add_action() # an error happened\n devm_drm_dev_init_release()\n drm_dev_put()\n kref_put()\n drm_dev_release()\n vkms_release()\n destroy_workqueue() # null-ptr-deref happened\n vkms_modeset_init()\n vkms_output_init()\n vkms_crtc_init() # where the workqueue get allocated\n\nFix this by checking if composer_workq is NULL before passing it to\nthe destroy_workqueue() in vkms_release()."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/0b8f390e2251191f1b179cc87f65d54c96565f0d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/1f9836f95271e7acf016667eee0aeae3386f9645",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2fe2a8f40c21161ffe7653cc234e7934db5b7cc5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/57031c474c3a920ea73afeb5dc352e537f5793ee",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/596f1ba3987e601e31a5abf1f75ce1d2635aceac",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50370.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2022-50370",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:35.950",
"lastModified": "2025-09-17T15:15:35.950",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: designware: Fix handling of real but unexpected device interrupts\n\nCommit c7b79a752871 (\"mfd: intel-lpss: Add Intel Alder Lake PCH-S PCI\nIDs\") caused a regression on certain Gigabyte motherboards for Intel\nAlder Lake-S where system crashes to NULL pointer dereference in\ni2c_dw_xfer_msg() when system resumes from S3 sleep state (\"deep\").\n\nI was able to debug the issue on Gigabyte Z690 AORUS ELITE and made\nfollowing notes:\n\n- Issue happens when resuming from S3 but not when resuming from\n \"s2idle\"\n- PCI device 00:15.0 == i2c_designware.0 is already in D0 state when\n system enters into pci_pm_resume_noirq() while all other i2c_designware\n PCI devices are in D3. Devices were runtime suspended and in D3 prior\n entering into suspend\n- Interrupt comes after pci_pm_resume_noirq() when device interrupts are\n re-enabled\n- According to register dump the interrupt really comes from the\n i2c_designware.0. Controller is enabled, I2C target address register\n points to a one detectable I2C device address 0x60 and the\n DW_IC_RAW_INTR_STAT register START_DET, STOP_DET, ACTIVITY and\n TX_EMPTY bits are set indicating completed I2C transaction.\n\nMy guess is that the firmware uses this controller to communicate with\nan on-board I2C device during resume but does not disable the controller\nbefore giving control to an operating system.\n\nI was told the UEFI update fixes this but never the less it revealed the\ndriver is not ready to handle TX_EMPTY (or RX_FULL) interrupt when device\nis supposed to be idle and state variables are not set (especially the\ndev->msgs pointer which may point to NULL or stale old data).\n\nIntroduce a new software status flag STATUS_ACTIVE indicating when the\ncontroller is active in driver point of view. Now treat all interrupts\nthat occur when is not set as unexpected and mask all interrupts from\nthe controller."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/301c8f5c32c8fb79c67539bc23972dc3ef48024c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7fa5304c4b5b425d4a0b3acf10139a7f6108a85f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a206f7fbe9589c60fafad12884628c909ecb042f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/aa59ac81e859006d3a1df035a19b3f2089110f93",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50371.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2022-50371",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.070",
"lastModified": "2025-09-17T15:15:36.070",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nled: qcom-lpg: Fix sleeping in atomic\n\nlpg_brighness_set() function can sleep, while led's brightness_set()\ncallback must be non-blocking. Change LPG driver to use\nbrightness_set_blocking() instead.\n\nBUG: sleeping function called from invalid context at kernel/locking/mutex.c:580\nin_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/0\npreempt_count: 101, expected: 0\nINFO: lockdep is turned off.\nCPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 6.1.0-rc1-00014-gbe99b089c6fc-dirty #85\nHardware name: Qualcomm Technologies, Inc. DB820c (DT)\nCall trace:\n dump_backtrace.part.0+0xe4/0xf0\n show_stack+0x18/0x40\n dump_stack_lvl+0x88/0xb4\n dump_stack+0x18/0x34\n __might_resched+0x170/0x254\n __might_sleep+0x48/0x9c\n __mutex_lock+0x4c/0x400\n mutex_lock_nested+0x2c/0x40\n lpg_brightness_single_set+0x40/0x90\n led_set_brightness_nosleep+0x34/0x60\n led_heartbeat_function+0x80/0x170\n call_timer_fn+0xb8/0x340\n __run_timers.part.0+0x20c/0x254\n run_timer_softirq+0x3c/0x7c\n _stext+0x14c/0x578\n ____do_softirq+0x10/0x20\n call_on_irq_stack+0x2c/0x5c\n do_softirq_own_stack+0x1c/0x30\n __irq_exit_rcu+0x164/0x170\n irq_exit_rcu+0x10/0x40\n el1_interrupt+0x38/0x50\n el1h_64_irq_handler+0x18/0x2c\n el1h_64_irq+0x64/0x68\n cpuidle_enter_state+0xc8/0x380\n cpuidle_enter+0x38/0x50\n do_idle+0x244/0x2d0\n cpu_startup_entry+0x24/0x30\n rest_init+0x128/0x1a0\n arch_post_acpi_subsys_init+0x0/0x18\n start_kernel+0x6f4/0x734\n __primary_switched+0xbc/0xc4"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/3031993b3474794ecb71b6f969a3e60e4bda9d8a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/380304391fa7fb084745f26b4b9a59f4666520c1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9deba7b51d5ee7a2d93fabb69f9b8189241f90e3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50372.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2022-50372",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.187",
"lastModified": "2025-09-17T15:15:36.187",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory leak when build ntlmssp negotiate blob failed\n\nThere is a memory leak when mount cifs:\n unreferenced object 0xffff888166059600 (size 448):\n comm \"mount.cifs\", pid 51391, jiffies 4295596373 (age 330.596s)\n hex dump (first 32 bytes):\n fe 53 4d 42 40 00 00 00 00 00 00 00 01 00 82 00 .SMB@...........\n 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n backtrace:\n [<0000000060609a61>] mempool_alloc+0xe1/0x260\n [<00000000adfa6c63>] cifs_small_buf_get+0x24/0x60\n [<00000000ebb404c7>] __smb2_plain_req_init+0x32/0x460\n [<00000000bcf875b4>] SMB2_sess_alloc_buffer+0xa4/0x3f0\n [<00000000753a2987>] SMB2_sess_auth_rawntlmssp_negotiate+0xf5/0x480\n [<00000000f0c1f4f9>] SMB2_sess_setup+0x253/0x410\n [<00000000a8b83303>] cifs_setup_session+0x18f/0x4c0\n [<00000000854bd16d>] cifs_get_smb_ses+0xae7/0x13c0\n [<000000006cbc43d9>] mount_get_conns+0x7a/0x730\n [<000000005922d816>] cifs_mount+0x103/0xd10\n [<00000000e33def3b>] cifs_smb3_do_mount+0x1dd/0xc90\n [<0000000078034979>] smb3_get_tree+0x1d5/0x300\n [<000000004371f980>] vfs_get_tree+0x41/0xf0\n [<00000000b670d8a7>] path_mount+0x9b3/0xdd0\n [<000000005e839a7d>] __x64_sys_mount+0x190/0x1d0\n [<000000009404c3b9>] do_syscall_64+0x35/0x80\n\nWhen build ntlmssp negotiate blob failed, the session setup request\nshould be freed."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/30b2d7f8f13664655480d6af45f60270b3eb6736",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/fa5a70bdd5e565c8696fb04dfe18a4e8aff4695d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50373.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2022-50373",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.303",
"lastModified": "2025-09-17T15:15:36.303",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs: dlm: fix race in lowcomms\n\nThis patch fixes a race between queue_work() in\n_dlm_lowcomms_commit_msg() and srcu_read_unlock(). The queue_work() can\ntake the final reference of a dlm_msg and so msg->idx can contain\ngarbage which is signaled by the following warning:\n\n[ 676.237050] ------------[ cut here ]------------\n[ 676.237052] WARNING: CPU: 0 PID: 1060 at include/linux/srcu.h:189 dlm_lowcomms_commit_msg+0x41/0x50\n[ 676.238945] Modules linked in: dlm_locktorture torture rpcsec_gss_krb5 intel_rapl_msr intel_rapl_common iTCO_wdt iTCO_vendor_support qxl kvm_intel drm_ttm_helper vmw_vsock_virtio_transport kvm vmw_vsock_virtio_transport_common ttm irqbypass crc32_pclmul joydev crc32c_intel serio_raw drm_kms_helper vsock virtio_scsi virtio_console virtio_balloon snd_pcm drm syscopyarea sysfillrect sysimgblt snd_timer fb_sys_fops i2c_i801 lpc_ich snd i2c_smbus soundcore pcspkr\n[ 676.244227] CPU: 0 PID: 1060 Comm: lock_torture_wr Not tainted 5.19.0-rc3+ #1546\n[ 676.245216] Hardware name: Red Hat KVM/RHEL-AV, BIOS 1.16.0-2.module+el8.7.0+15506+033991b0 04/01/2014\n[ 676.246460] RIP: 0010:dlm_lowcomms_commit_msg+0x41/0x50\n[ 676.247132] Code: fe ff ff ff 75 24 48 c7 c6 bd 0f 49 bb 48 c7 c7 38 7c 01 bd e8 00 e7 ca ff 89 de 48 c7 c7 60 78 01 bd e8 42 3d cd ff 5b 5d c3 <0f> 0b eb d8 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48\n[ 676.249253] RSP: 0018:ffffa401c18ffc68 EFLAGS: 00010282\n[ 676.249855] RAX: 0000000000000001 RBX: 00000000ffff8b76 RCX: 0000000000000006\n[ 676.250713] RDX: 0000000000000000 RSI: ffffffffbccf3a10 RDI: ffffffffbcc7b62e\n[ 676.251610] RBP: ffffa401c18ffc70 R08: 0000000000000001 R09: 0000000000000001\n[ 676.252481] R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000005\n[ 676.253421] R13: ffff8b76786ec370 R14: ffff8b76786ec370 R15: ffff8b76786ec480\n[ 676.254257] FS: 0000000000000000(0000) GS:ffff8b7777800000(0000) knlGS:0000000000000000\n[ 676.255239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 676.255897] CR2: 00005590205d88b8 CR3: 000000017656c003 CR4: 0000000000770ee0\n[ 676.256734] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 676.257567] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 676.258397] PKRU: 55555554\n[ 676.258729] Call Trace:\n[ 676.259063] <TASK>\n[ 676.259354] dlm_midcomms_commit_mhandle+0xcc/0x110\n[ 676.259964] queue_bast+0x8b/0xb0\n[ 676.260423] grant_pending_locks+0x166/0x1b0\n[ 676.261007] _unlock_lock+0x75/0x90\n[ 676.261469] unlock_lock.isra.57+0x62/0xa0\n[ 676.262009] dlm_unlock+0x21e/0x330\n[ 676.262457] ? lock_torture_stats+0x80/0x80 [dlm_locktorture]\n[ 676.263183] torture_unlock+0x5a/0x90 [dlm_locktorture]\n[ 676.263815] ? preempt_count_sub+0xba/0x100\n[ 676.264361] ? complete+0x1d/0x60\n[ 676.264777] lock_torture_writer+0xb8/0x150 [dlm_locktorture]\n[ 676.265555] kthread+0x10a/0x130\n[ 676.266007] ? kthread_complete_and_exit+0x20/0x20\n[ 676.266616] ret_from_fork+0x22/0x30\n[ 676.267097] </TASK>\n[ 676.267381] irq event stamp: 9579855\n[ 676.267824] hardirqs last enabled at (9579863): [<ffffffffbb14e6f8>] __up_console_sem+0x58/0x60\n[ 676.268896] hardirqs last disabled at (9579872): [<ffffffffbb14e6dd>] __up_console_sem+0x3d/0x60\n[ 676.270008] softirqs last enabled at (9579798): [<ffffffffbc200349>] __do_softirq+0x349/0x4c7\n[ 676.271438] softirqs last disabled at (9579897): [<ffffffffbb0d54c0>] irq_exit_rcu+0xb0/0xf0\n[ 676.272796] ---[ end trace 0000000000000000 ]---\n\nI reproduced this warning with dlm_locktorture test which is currently\nnot upstream. However this patch fix the issue by make a additional\nrefcount between dlm_lowcomms_new_msg() and dlm_lowcomms_commit_msg().\nIn case of the race the kref_put() in dlm_lowcomms_commit_msg() will be\nthe final put."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/27d3e646dd83bafd7094890462eebfce3ac31e4a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/30ea3257e8766027c4d8d609dcbd256ff9a76073",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/de7fdff754bb4d01e38e19964c309b6df6a79472",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/eb97e60a9eae632ff9104a580dbc4fdc58dc23cb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2022/CVE-2022-503xx/CVE-2022-50374.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2022-50374",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.427",
"lastModified": "2025-09-17T15:15:36.427",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure\n\nsyzbot is reporting NULL pointer dereference at hci_uart_tty_close() [1],\nfor rcu_sync_enter() is called without rcu_sync_init() due to\nhci_uart_tty_open() ignoring percpu_init_rwsem() failure.\n\nWhile we are at it, fix that hci_uart_register_device() ignores\npercpu_init_rwsem() failure and hci_uart_unregister_device() does not\ncall percpu_free_rwsem()."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/3124d320c22f3f4388d9ac5c8f37eaad0cefd6b1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/75b2c71ea581c7bb1303860d89366a42ad0506d2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/98ce10f3f345e61fc6c83bff9cd11cda252b05ac",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b8917dce2134739b39bc0a5648b18427f2cad569",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d7cc0d51ffcbfd1caaa809fcf9cff05c46d0fb4d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53304.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53304",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:35.240",
"lastModified": "2025-09-16T17:15:35.240",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53305.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53305",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.260",
"lastModified": "2025-09-16T17:15:36.260",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53306.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53306",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.370",
"lastModified": "2025-09-16T17:15:36.370",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53307.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53307",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.477",
"lastModified": "2025-09-16T17:15:36.477",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53308.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53308",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.597",
"lastModified": "2025-09-16T17:15:36.597",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53309.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53309",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.720",
"lastModified": "2025-09-16T17:15:36.720",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53310.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53310",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.847",
"lastModified": "2025-09-16T17:15:36.847",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53311.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53311",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:36.967",
"lastModified": "2025-09-16T17:15:36.967",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53312.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53312",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.117",
"lastModified": "2025-09-16T17:15:37.117",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53313.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53313",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.233",
"lastModified": "2025-09-16T17:15:37.233",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53314.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53314",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.360",
"lastModified": "2025-09-16T17:15:37.360",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53315.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53315",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.480",
"lastModified": "2025-09-16T17:15:37.480",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53316.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53316",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.600",
"lastModified": "2025-09-16T17:15:37.600",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53317.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53317",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.713",
"lastModified": "2025-09-16T17:15:37.713",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53318.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53318",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.833",
"lastModified": "2025-09-16T17:15:37.833",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53319.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53319",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:37.947",
"lastModified": "2025-09-16T17:15:37.947",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53320.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53320",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.050",
"lastModified": "2025-09-16T17:15:38.050",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53321.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53321",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.173",
"lastModified": "2025-09-16T17:15:38.173",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53322.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53322",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.287",
"lastModified": "2025-09-16T17:15:38.287",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53323.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53323",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.410",
"lastModified": "2025-09-16T17:15:38.410",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53324.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53324",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.520",
"lastModified": "2025-09-16T17:15:38.520",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53325.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53325",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.657",
"lastModified": "2025-09-16T17:15:38.657",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53326.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53326",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.783",
"lastModified": "2025-09-16T17:15:38.783",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53327.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53327",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:38.910",
"lastModified": "2025-09-16T17:15:38.910",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53328.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53328",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.053",
"lastModified": "2025-09-16T17:15:39.053",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53329.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53329",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.207",
"lastModified": "2025-09-16T17:15:39.207",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53330.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53330",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.313",
"lastModified": "2025-09-16T17:15:39.313",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53331.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53331",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.597",
"lastModified": "2025-09-16T17:15:39.597",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53332.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53332",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.730",
"lastModified": "2025-09-16T17:15:39.730",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53333.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53333",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.837",
"lastModified": "2025-09-16T17:15:39.837",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53334.json
+2 -2
View File
@@ -2,8 +2,8 @@
"id": "CVE-2023-53334",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-16T17:15:39.957",
"lastModified": "2025-09-16T17:15:39.957",
"vulnStatus": "Received",
"lastModified": "2025-09-17T14:18:55.093",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
CVE-2023/CVE-2023-533xx/CVE-2023-53335.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2023-53335",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.560",
"lastModified": "2025-09-17T15:15:36.560",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cxgb4: Fix potential null-ptr-deref in pass_establish()\n\nIf get_ep_from_tid() fails to lookup non-NULL value for ep, ep is\ndereferenced later regardless of whether it is empty.\nThis patch adds a simple sanity check to fix the issue.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/283861a4c52c1ea4df3dd1b6fc75a50796ce3524",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2cfc00e974d75a3aa8155f2660f57d342e1f67ca",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9dca64042d855a24b0bd81ce242e5dc7e939f6eb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9ddc77eefb2a567b705c3c86ab2ddabe43cadf1b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53336.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53336",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.680",
"lastModified": "2025-09-17T15:15:36.680",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ipu-bridge: Fix null pointer deref on SSDB/PLD parsing warnings\n\nWhen ipu_bridge_parse_rotation() and ipu_bridge_parse_orientation() run\nsensor->adev is not set yet.\n\nSo if either of the dev_warn() calls about unknown values are hit this\nwill lead to a NULL pointer deref.\n\nSet sensor->adev earlier, with a borrowed ref to avoid making unrolling\non errors harder, to fix this."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/284be5693163343e1cf17c03917eecd1d6681bcf",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3de35e29cfddfe6bff762b15bcfe8d80bebac6cb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e08b091e33ecf6e4cb2c0c5820a69abe7673280b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53337.json
+53
View File
@@ -0,0 +1,53 @@
{
"id": "CVE-2023-53337",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.793",
"lastModified": "2025-09-17T15:15:36.793",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: do not write dirty data after degenerating to read-only\n\nAccording to syzbot's report, mark_buffer_dirty() called from\nnilfs_segctor_do_construct() outputs a warning with some patterns after\nnilfs2 detects metadata corruption and degrades to read-only mode.\n\nAfter such read-only degeneration, page cache data may be cleared through\nnilfs_clear_dirty_page() which may also clear the uptodate flag for their\nbuffer heads. However, even after the degeneration, log writes are still\nperformed by unmount processing etc., which causes mark_buffer_dirty() to\nbe called for buffer heads without the \"uptodate\" flag and causes the\nwarning.\n\nSince any writes should not be done to a read-only file system in the\nfirst place, this fixes the warning in mark_buffer_dirty() by letting\nnilfs_segctor_do_construct() abort early if in read-only mode.\n\nThis also changes the retry check of nilfs_segctor_write_out() to avoid\nunnecessary log write retries if it detects -EROFS that\nnilfs_segctor_do_construct() returned."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/13f73ef77baa4764dc1ca4fcbae9cade05b83866",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/28a65b49eb53e172d23567005465019658bfdb4d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4005cec6847c06ee191583270b7cdd7e696543cc",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4569a292a84e340e97d178898ad1cfe1a3080a61",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/55f7810632f993cff622a0ddbc7c865892294b61",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7c3e662048053802f6b0db3a78e97f4e1f7edc4f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a73201c607d8e506358d60aafddda4246bdd9350",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bd89073fc7a5d03b1d06b372addbe405e5a925f4",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e9c5412c5972124776c1b873533eb39e287a4dfa",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53338.json
+45
View File
@@ -0,0 +1,45 @@
{
"id": "CVE-2023-53338",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:36.913",
"lastModified": "2025-09-17T15:15:36.913",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nlwt: Fix return values of BPF xmit ops\n\nBPF encap ops can return different types of positive values, such like\nNET_RX_DROP, NET_XMIT_CN, NETDEV_TX_BUSY, and so on, from function\nskb_do_redirect and bpf_lwt_xmit_reroute. At the xmit hook, such return\nvalues would be treated implicitly as LWTUNNEL_XMIT_CONTINUE in\nip(6)_finish_output2. When this happens, skbs that have been freed would\ncontinue to the neighbor subsystem, causing use-after-free bug and\nkernel crashes.\n\nTo fix the incorrect behavior, skb_do_redirect return values can be\nsimply discarded, the same as tc-egress behavior. On the other hand,\nbpf_lwt_xmit_reroute returns useful errors to local senders, e.g. PMTU\ninformation. Thus convert its return values to avoid the conflict with\nLWTUNNEL_XMIT_CONTINUE."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/065d5f17096ec9161180e2c890afdff4dc6125f2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/29b22badb7a84b783e3a4fffca16f7768fb31205",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/65583f9e070db7bece20710cfa2e3daeb0b831d9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/67f8f2bae8e7ac72e09def2b667e44704c4d1ee1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a97f221651fcdc891166e9bc270e3d9bfa5a0080",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d68c17402442f5f494a2c3ebde5cb82f6aa9160a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e3f647e4b642f9f6d32795a16f92c116c138d2af",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53339.json
+45
View File
@@ -0,0 +1,45 @@
{
"id": "CVE-2023-53339",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:37.030",
"lastModified": "2025-09-17T15:15:37.030",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix BUG_ON condition in btrfs_cancel_balance\n\nPausing and canceling balance can race to interrupt balance lead to BUG_ON\npanic in btrfs_cancel_balance. The BUG_ON condition in btrfs_cancel_balance\ndoes not take this race scenario into account.\n\nHowever, the race condition has no other side effects. We can fix that.\n\nReproducing it with panic trace like this:\n\n kernel BUG at fs/btrfs/volumes.c:4618!\n RIP: 0010:btrfs_cancel_balance+0x5cf/0x6a0\n Call Trace:\n <TASK>\n ? do_nanosleep+0x60/0x120\n ? hrtimer_nanosleep+0xb7/0x1a0\n ? sched_core_clone_cookie+0x70/0x70\n btrfs_ioctl_balance_ctl+0x55/0x70\n btrfs_ioctl+0xa46/0xd20\n __x64_sys_ioctl+0x7d/0xa0\n do_syscall_64+0x38/0x80\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n Race scenario as follows:\n > mutex_unlock(&fs_info->balance_mutex);\n > --------------------\n > .......issue pause and cancel req in another thread\n > --------------------\n > ret = __btrfs_balance(fs_info);\n >\n > mutex_lock(&fs_info->balance_mutex);\n > if (ret == -ECANCELED && atomic_read(&fs_info->balance_pause_req)) {\n > btrfs_info(fs_info, \"balance: paused\");\n > btrfs_exclop_balance(fs_info, BTRFS_EXCLOP_BALANCE_PAUSED);\n > }"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/29eefa6d0d07e185f7bfe9576f91e6dba98189c2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7c93b89cd46636b5e74c12fa21dd86167bc6ea8d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a0a462a0f20926918d6009f0b4b25673e883fc98",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ae81329f7de3aa6f34ecdfa5412e72161a30e9ce",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b966e9e1e250dfdb41a7f41775faea4a37af923c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bd7bef82ce0e929ef4cf63a34990545aaca28077",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ceb9ba8e30833a4823e2dc73f80ebcdf2498d01a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53340.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53340",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:37.153",
"lastModified": "2025-09-17T15:15:37.153",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Collect command failures data only for known commands\n\nDEVX can issue a general command, which is not used by mlx5 driver.\nIn case such command is failed, mlx5 is trying to collect the failure\ndata, However, mlx5 doesn't create a storage for this command, since\nmlx5 doesn't use it. This lead to array-index-out-of-bounds error.\n\nFix it by checking whether the command is known before collecting the\nfailure data."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2a0a935fb64ee8af253b9c6133bb6702fb152ac2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/411e4d6caa7f7169192b8dacc8421ac4fd64a354",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d8b6f175235d7327b4e1b13216859e89496dfbd5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53341.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53341",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:37.273",
"lastModified": "2025-09-17T15:15:37.273",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nof/fdt: run soc memory setup when early_init_dt_scan_memory fails\n\nIf memory has been found early_init_dt_scan_memory now returns 1. If\nit hasn't found any memory it will return 0, allowing other memory\nsetup mechanisms to carry on.\n\nPreviously early_init_dt_scan_memory always returned 0 without\ndistinguishing between any kind of memory setup being done or not. Any\ncode path after the early_init_dt_scan memory call in the ramips\nplat_mem_setup code wouldn't be executed anymore. Making\nearly_init_dt_scan_memory the only way to initialize the memory.\n\nSome boards, including my mt7621 based Cudy X6 board, depend on memory\ninitialization being done via the soc_info.mem_detect function\npointer. Those wouldn't be able to obtain memory and panic the kernel\nduring early bootup with the message \"early_init_dt_alloc_memory_arch:\nFailed to allocate 12416 bytes align=0x40\"."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/04836fc5b720dfa32ff781383d84f63019abf9b9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2a12187d5853d9fd5102278cecef7dac7c8ce7ea",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c4849f18185fd4e93b04cd45552f8d68c0240e21",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53342.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53342",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:37.393",
"lastModified": "2025-09-17T15:15:37.393",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: marvell: prestera: fix handling IPv4 routes with nhid\n\nFix handling IPv4 routes referencing a nexthop via its id by replacing\ncalls to fib_info_nh() with fib_info_nhc().\n\nTrying to add an IPv4 route referencing a nextop via nhid:\n\n $ ip link set up swp5\n $ ip a a 10.0.0.1/24 dev swp5\n $ ip nexthop add dev swp5 id 20 via 10.0.0.2\n $ ip route add 10.0.1.0/24 nhid 20\n\ntriggers warnings when trying to handle the route:\n\n[ 528.805763] ------------[ cut here ]------------\n[ 528.810437] WARNING: CPU: 3 PID: 53 at include/net/nexthop.h:468 __prestera_fi_is_direct+0x2c/0x68 [prestera]\n[ 528.820434] Modules linked in: prestera_pci act_gact act_police sch_ingress cls_u32 cls_flower prestera arm64_delta_tn48m_dn_led(O) arm64_delta_tn48m_dn_cpld(O) [last unloaded: prestera_pci]\n[ 528.837485] CPU: 3 PID: 53 Comm: kworker/u8:3 Tainted: G O 6.4.5 #1\n[ 528.845178] Hardware name: delta,tn48m-dn (DT)\n[ 528.849641] Workqueue: prestera_ordered __prestera_router_fib_event_work [prestera]\n[ 528.857352] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 528.864347] pc : __prestera_fi_is_direct+0x2c/0x68 [prestera]\n[ 528.870135] lr : prestera_k_arb_fib_evt+0xb20/0xd50 [prestera]\n[ 528.876007] sp : ffff80000b20bc90\n[ 528.879336] x29: ffff80000b20bc90 x28: 0000000000000000 x27: ffff0001374d3a48\n[ 528.886510] x26: ffff000105604000 x25: ffff000134af8a28 x24: ffff0001374d3800\n[ 528.893683] x23: ffff000101c89148 x22: ffff000101c89000 x21: ffff000101c89200\n[ 528.900855] x20: ffff00013641fda0 x19: ffff800009d01088 x18: 0000000000000059\n[ 528.908027] x17: 0000000000000277 x16: 0000000000000000 x15: 0000000000000000\n[ 528.915198] x14: 0000000000000003 x13: 00000000000fe400 x12: 0000000000000000\n[ 528.922371] x11: 0000000000000002 x10: 0000000000000aa0 x9 : ffff8000013d2020\n[ 528.929543] x8 : 0000000000000018 x7 : 000000007b1703f8 x6 : 000000001ca72f86\n[ 528.936715] x5 : 0000000033399ea7 x4 : 0000000000000000 x3 : ffff0001374d3acc\n[ 528.943886] x2 : 0000000000000000 x1 : ffff00010200de00 x0 : ffff000134ae3f80\n[ 528.951058] Call trace:\n[ 528.953516] __prestera_fi_is_direct+0x2c/0x68 [prestera]\n[ 528.958952] __prestera_router_fib_event_work+0x100/0x158 [prestera]\n[ 528.965348] process_one_work+0x208/0x488\n[ 528.969387] worker_thread+0x4c/0x430\n[ 528.973068] kthread+0x120/0x138\n[ 528.976313] ret_from_fork+0x10/0x20\n[ 528.979909] ---[ end trace 0000000000000000 ]---\n[ 528.984998] ------------[ cut here ]------------\n[ 528.989645] WARNING: CPU: 3 PID: 53 at include/net/nexthop.h:468 __prestera_fi_is_direct+0x2c/0x68 [prestera]\n[ 528.999628] Modules linked in: prestera_pci act_gact act_police sch_ingress cls_u32 cls_flower prestera arm64_delta_tn48m_dn_led(O) arm64_delta_tn48m_dn_cpld(O) [last unloaded: prestera_pci]\n[ 529.016676] CPU: 3 PID: 53 Comm: kworker/u8:3 Tainted: G W O 6.4.5 #1\n[ 529.024368] Hardware name: delta,tn48m-dn (DT)\n[ 529.028830] Workqueue: prestera_ordered __prestera_router_fib_event_work [prestera]\n[ 529.036539] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 529.043533] pc : __prestera_fi_is_direct+0x2c/0x68 [prestera]\n[ 529.049318] lr : __prestera_k_arb_fc_apply+0x280/0x2f8 [prestera]\n[ 529.055452] sp : ffff80000b20bc60\n[ 529.058781] x29: ffff80000b20bc60 x28: 0000000000000000 x27: ffff0001374d3a48\n[ 529.065953] x26: ffff000105604000 x25: ffff000134af8a28 x24: ffff0001374d3800\n[ 529.073126] x23: ffff000101c89148 x22: ffff000101c89148 x21: ffff00013641fda0\n[ 529.080299] x20: ffff000101c89000 x19: ffff000101c89020 x18: 0000000000000059\n[ 529.087471] x17: 0000000000000277 x16: 0000000000000000 x15: 0000000000000000\n[ 529.094642] x14: 0000000000000003 x13: 00000000000fe400 x12: 0000000000000000\n[ 529.101814] x11: 0000000000000002 x10: 0000000000000aa0 x9 : ffff8000013cee80\n[ 529.108985] x8 : 0000000000000018 x7 : 000000007b1703f8 x6 \n---truncated---"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2aa71b4b294ee2c3041d085404cea914be9b3225",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8373dca3c1f8a203cecebe3421dbe890c4f08e16",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a3e5f3b7f25d7b90f3b76d98a946fec6e5f79216",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53343.json
+45
View File
@@ -0,0 +1,45 @@
{
"id": "CVE-2023-53343",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.100",
"lastModified": "2025-09-17T15:15:38.100",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nicmp6: Fix null-ptr-deref of ip6_null_entry->rt6i_idev in icmp6_dev().\n\nWith some IPv6 Ext Hdr (RPL, SRv6, etc.), we can send a packet that\nhas the link-local address as src and dst IP and will be forwarded to\nan external IP in the IPv6 Ext Hdr.\n\nFor example, the script below generates a packet whose src IP is the\nlink-local address and dst is updated to 11::.\n\n # for f in $(find /proc/sys/net/ -name *seg6_enabled*); do echo 1 > $f; done\n # python3\n >>> from socket import *\n >>> from scapy.all import *\n >>>\n >>> SRC_ADDR = DST_ADDR = \"fe80::5054:ff:fe12:3456\"\n >>>\n >>> pkt = IPv6(src=SRC_ADDR, dst=DST_ADDR)\n >>> pkt /= IPv6ExtHdrSegmentRouting(type=4, addresses=[\"11::\", \"22::\"], segleft=1)\n >>>\n >>> sk = socket(AF_INET6, SOCK_RAW, IPPROTO_RAW)\n >>> sk.sendto(bytes(pkt), (DST_ADDR, 0))\n\nFor such a packet, we call ip6_route_input() to look up a route for the\nnext destination in these three functions depending on the header type.\n\n * ipv6_rthdr_rcv()\n * ipv6_rpl_srh_rcv()\n * ipv6_srh_rcv()\n\nIf no route is found, ip6_null_entry is set to skb, and the following\ndst_input(skb) calls ip6_pkt_drop().\n\nFinally, in icmp6_dev(), we dereference skb_rt6_info(skb)->rt6i_idev->dev\nas the input device is the loopback interface. Then, we have to check if\nskb_rt6_info(skb)->rt6i_idev is NULL or not to avoid NULL pointer deref\nfor ip6_null_entry.\n\nBUG: kernel NULL pointer dereference, address: 0000000000000000\n PF: supervisor read access in kernel mode\n PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 0 PID: 157 Comm: python3 Not tainted 6.4.0-11996-gb121d614371c #35\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:icmp6_send (net/ipv6/icmp.c:436 net/ipv6/icmp.c:503)\nCode: fe ff ff 48 c7 40 30 c0 86 5d 83 e8 c6 44 1c 00 e9 c8 fc ff ff 49 8b 46 58 48 83 e0 fe 0f 84 4a fb ff ff 48 8b 80 d0 00 00 00 <48> 8b 00 44 8b 88 e0 00 00 00 e9 34 fb ff ff 4d 85 ed 0f 85 69 01\nRSP: 0018:ffffc90000003c70 EFLAGS: 00000286\nRAX: 0000000000000000 RBX: 0000000000000001 RCX: 00000000000000e0\nRDX: 0000000000000021 RSI: 0000000000000000 RDI: ffff888006d72a18\nRBP: ffffc90000003d80 R08: 0000000000000000 R09: 0000000000000001\nR10: ffffc90000003d98 R11: 0000000000000040 R12: ffff888006d72a10\nR13: 0000000000000000 R14: ffff8880057fb800 R15: ffffffff835d86c0\nFS: 00007f9dc72ee740(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000057b2000 CR4: 00000000007506f0\nPKRU: 55555554\nCall Trace:\n <IRQ>\n ip6_pkt_drop (net/ipv6/route.c:4513)\n ipv6_rthdr_rcv (net/ipv6/exthdrs.c:640 net/ipv6/exthdrs.c:686)\n ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:437 (discriminator 5))\n ip6_input_finish (./include/linux/rcupdate.h:781 net/ipv6/ip6_input.c:483)\n __netif_receive_skb_one_core (net/core/dev.c:5455)\n process_backlog (./include/linux/rcupdate.h:781 net/core/dev.c:5895)\n __napi_poll (net/core/dev.c:6460)\n net_rx_action (net/core/dev.c:6529 net/core/dev.c:6660)\n __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:554)\n do_softirq (kernel/softirq.c:454 kernel/softirq.c:441)\n </IRQ>\n <TASK>\n __local_bh_enable_ip (kernel/softirq.c:381)\n __dev_queue_xmit (net/core/dev.c:4231)\n ip6_finish_output2 (./include/net/neighbour.h:544 net/ipv6/ip6_output.c:135)\n rawv6_sendmsg (./include/net/dst.h:458 ./include/linux/netfilter.h:303 net/ipv6/raw.c:656 net/ipv6/raw.c:914)\n sock_sendmsg (net/socket.c:725 net/socket.c:748)\n __sys_sendto (net/socket.c:2134)\n __x64_sys_sendto (net/socket.c:2146 net/socket.c:2142 net/socket.c:2142)\n do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)\nRIP: 0033:0x7f9dc751baea\nCode: d8 64 89 02 48 c7 c0 ff f\n---truncated---"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1462e9d9aa52d14665eaca6d89d22c4af44ede04",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2aaa8a15de73874847d62eb595c6683bface80fd",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3fabca5d9cae0140b6aad09a1c6b9aa57089fbb8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/61b4c4659746959056450b92a5d7e6bc1243b31b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8803c59fde4dd370a627dfbf7183682fa0cabf70",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/aa657d319e6c7502a4eb85cc0ee80cc81b8e5724",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d30ddd7ff15df9d91a793ce3f06f0190ff7afacc",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53344.json
+49
View File
@@ -0,0 +1,49 @@
{
"id": "CVE-2023-53344",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.237",
"lastModified": "2025-09-17T15:15:38.237",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write\n\nSyzkaller reported the following issue:\n\n=====================================================\nBUG: KMSAN: uninit-value in aio_rw_done fs/aio.c:1520 [inline]\nBUG: KMSAN: uninit-value in aio_write+0x899/0x950 fs/aio.c:1600\n aio_rw_done fs/aio.c:1520 [inline]\n aio_write+0x899/0x950 fs/aio.c:1600\n io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019\n __do_sys_io_submit fs/aio.c:2078 [inline]\n __se_sys_io_submit+0x293/0x770 fs/aio.c:2048\n __x64_sys_io_submit+0x92/0xd0 fs/aio.c:2048\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nUninit was created at:\n slab_post_alloc_hook mm/slab.h:766 [inline]\n slab_alloc_node mm/slub.c:3452 [inline]\n __kmem_cache_alloc_node+0x71f/0xce0 mm/slub.c:3491\n __do_kmalloc_node mm/slab_common.c:967 [inline]\n __kmalloc+0x11d/0x3b0 mm/slab_common.c:981\n kmalloc_array include/linux/slab.h:636 [inline]\n bcm_tx_setup+0x80e/0x29d0 net/can/bcm.c:930\n bcm_sendmsg+0x3a2/0xce0 net/can/bcm.c:1351\n sock_sendmsg_nosec net/socket.c:714 [inline]\n sock_sendmsg net/socket.c:734 [inline]\n sock_write_iter+0x495/0x5e0 net/socket.c:1108\n call_write_iter include/linux/fs.h:2189 [inline]\n aio_write+0x63a/0x950 fs/aio.c:1600\n io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019\n __do_sys_io_submit fs/aio.c:2078 [inline]\n __se_sys_io_submit+0x293/0x770 fs/aio.c:2048\n __x64_sys_io_submit+0x92/0xd0 fs/aio.c:2048\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nCPU: 1 PID: 5034 Comm: syz-executor350 Not tainted 6.2.0-rc6-syzkaller-80422-geda666ff2276 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023\n=====================================================\n\nWe can follow the call chain and find that 'bcm_tx_setup' function\ncalls 'memcpy_from_msg' to copy some content to the newly allocated\nframe of 'op->frames'. After that the 'len' field of copied structure\nbeing compared with some constant value (64 or 8). However, if\n'memcpy_from_msg' returns an error, we will compare some uninitialized\nmemory. This triggers 'uninit-value' issue.\n\nThis patch will add 'memcpy_from_msg' possible errors processing to\navoid uninit-value issue.\n\nTested via syzkaller"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2b4c99f7d9a57ecd644eda9b1fb0a1072414959f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2e6ad51c709fa794e0ce26003c9c9cd944e3383a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3fa0f1e0e31b1b73cdf59d4c36c7242e6ef821be",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/618b15d09fed6126356101543451d49860db4388",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/78bc7f0ab99458221224d3ab97199c0f8e6861f1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ab2a55907823f0bca56b6d03ea05e4071ba8535f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bf70e0eab64c625da84d9fdf4e84466b79418920",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c11dbc7705b3739974ac31a13f4ab81e61a5fb07",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53345.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53345",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.363",
"lastModified": "2025-09-17T15:15:38.363",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: Fix potential data race in rxrpc_wait_to_be_connected()\n\nInside the loop in rxrpc_wait_to_be_connected() it checks call->error to\nsee if it should exit the loop without first checking the call state. This\nis probably safe as if call->error is set, the call is dead anyway, but we\nshould probably wait for the call state to have been set to completion\nfirst, lest it cause surprise on the way out.\n\nFix this by only accessing call->error if the call is complete. We don't\nactually need to access the error inside the loop as we'll do that after.\n\nThis caused the following report:\n\n BUG: KCSAN: data-race in rxrpc_send_data / rxrpc_set_call_completion\n\n write to 0xffff888159cf3c50 of 4 bytes by task 25673 on cpu 1:\n rxrpc_set_call_completion+0x71/0x1c0 net/rxrpc/call_state.c:22\n rxrpc_send_data_packet+0xba9/0x1650 net/rxrpc/output.c:479\n rxrpc_transmit_one+0x1e/0x130 net/rxrpc/output.c:714\n rxrpc_decant_prepared_tx net/rxrpc/call_event.c:326 [inline]\n rxrpc_transmit_some_data+0x496/0x600 net/rxrpc/call_event.c:350\n rxrpc_input_call_event+0x564/0x1220 net/rxrpc/call_event.c:464\n rxrpc_io_thread+0x307/0x1d80 net/rxrpc/io_thread.c:461\n kthread+0x1ac/0x1e0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308\n\n read to 0xffff888159cf3c50 of 4 bytes by task 25672 on cpu 0:\n rxrpc_send_data+0x29e/0x1950 net/rxrpc/sendmsg.c:296\n rxrpc_do_sendmsg+0xb7a/0xc20 net/rxrpc/sendmsg.c:726\n rxrpc_sendmsg+0x413/0x520 net/rxrpc/af_rxrpc.c:565\n sock_sendmsg_nosec net/socket.c:724 [inline]\n sock_sendmsg net/socket.c:747 [inline]\n ____sys_sendmsg+0x375/0x4c0 net/socket.c:2501\n ___sys_sendmsg net/socket.c:2555 [inline]\n __sys_sendmmsg+0x263/0x500 net/socket.c:2641\n __do_sys_sendmmsg net/socket.c:2670 [inline]\n __se_sys_sendmmsg net/socket.c:2667 [inline]\n __x64_sys_sendmmsg+0x57/0x60 net/socket.c:2667\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n value changed: 0x00000000 -> 0xffffffea"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2b5fdc0f5caa505afe34d608e2eefadadf2ee67a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3e8ba61a3fe4475a9b5c9fbfc664435c6795d872",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/454e48a9ff04c5fa1631bb172070fcb6389b97f9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53346.json
+41
View File
@@ -0,0 +1,41 @@
{
"id": "CVE-2023-53346",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.480",
"lastModified": "2025-09-17T15:15:38.480",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nkernel/fail_function: fix memory leak with using debugfs_lookup()\n\nWhen calling debugfs_lookup() the result must have dput() called on it,\notherwise the memory will leak over time. To make things simpler, just\ncall debugfs_lookup_and_remove() instead which handles all of the logic\nat once."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/29d53c4c5a6f6d2b93aaac95b65cb4c907faf2ff",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2bb3669f576559db273efe49e0e69f82450efbca",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/94f68f3e059c478e240f65fcb64746fe371295df",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bb99db06b8b6ce9351633fc61bec9919d8f6f52b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/dd9981a11d74ff2eb253bb5c459876f8bd3c6c36",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f6d3aee1c66358471275df9dddd480010f061b0e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53347.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53347",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.603",
"lastModified": "2025-09-17T15:15:38.603",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Handle pairing of E-switch via uplink un/load APIs\n\nIn case user switch a device from switchdev mode to legacy mode, mlx5\nfirst unpair the E-switch and afterwards unload the uplink vport.\nFrom the other hand, in case user remove or reload a device, mlx5\nfirst unload the uplink vport and afterwards unpair the E-switch.\n\nThe latter is causing a bug[1], hence, handle pairing of E-switch as\npart of uplink un/load APIs.\n\n[1]\nIn case VF_LAG is used, every tc fdb flow is duplicated to the peer\nesw. However, the original esw keeps a pointer to this duplicated\nflow, not the peer esw.\ne.g.: if user create tc fdb flow over esw0, the flow is duplicated\nover esw1, in FW/HW, but in SW, esw0 keeps a pointer to the duplicated\nflow.\nDuring module unload while a peer tc fdb flow is still offloaded, in\ncase the first device to be removed is the peer device (esw1 in the\nexample above), the peer net-dev is destroyed, and so the mlx5e_priv\nis memset to 0.\nAfterwards, the peer device is trying to unpair himself from the\noriginal device (esw0 in the example above). Unpair API invoke the\noriginal device to clear peer flow from its eswitch (esw0), but the\npeer flow, which is stored over the original eswitch (esw0), is\ntrying to use the peer mlx5e_priv, which is memset to 0 and result in\nbellow kernel-oops.\n\n[ 157.964081 ] BUG: unable to handle page fault for address: 000000000002ce60\n[ 157.964662 ] #PF: supervisor read access in kernel mode\n[ 157.965123 ] #PF: error_code(0x0000) - not-present page\n[ 157.965582 ] PGD 0 P4D 0\n[ 157.965866 ] Oops: 0000 [#1] SMP\n[ 157.967670 ] RIP: 0010:mlx5e_tc_del_fdb_flow+0x48/0x460 [mlx5_core]\n[ 157.976164 ] Call Trace:\n[ 157.976437 ] <TASK>\n[ 157.976690 ] __mlx5e_tc_del_fdb_peer_flow+0xe6/0x100 [mlx5_core]\n[ 157.977230 ] mlx5e_tc_clean_fdb_peer_flows+0x67/0x90 [mlx5_core]\n[ 157.977767 ] mlx5_esw_offloads_unpair+0x2d/0x1e0 [mlx5_core]\n[ 157.984653 ] mlx5_esw_offloads_devcom_event+0xbf/0x130 [mlx5_core]\n[ 157.985212 ] mlx5_devcom_send_event+0xa3/0xb0 [mlx5_core]\n[ 157.985714 ] esw_offloads_disable+0x5a/0x110 [mlx5_core]\n[ 157.986209 ] mlx5_eswitch_disable_locked+0x152/0x170 [mlx5_core]\n[ 157.986757 ] mlx5_eswitch_disable+0x51/0x80 [mlx5_core]\n[ 157.987248 ] mlx5_unload+0x2a/0xb0 [mlx5_core]\n[ 157.987678 ] mlx5_uninit_one+0x5f/0xd0 [mlx5_core]\n[ 157.988127 ] remove_one+0x64/0xe0 [mlx5_core]\n[ 157.988549 ] pci_device_remove+0x31/0xa0\n[ 157.988933 ] device_release_driver_internal+0x18f/0x1f0\n[ 157.989402 ] driver_detach+0x3f/0x80\n[ 157.989754 ] bus_remove_driver+0x70/0xf0\n[ 157.990129 ] pci_unregister_driver+0x34/0x90\n[ 157.990537 ] mlx5_cleanup+0xc/0x1c [mlx5_core]\n[ 157.990972 ] __x64_sys_delete_module+0x15a/0x250\n[ 157.991398 ] ? exit_to_user_mode_prepare+0xea/0x110\n[ 157.991840 ] do_syscall_64+0x3d/0x90\n[ 157.992198 ] entry_SYSCALL_64_after_hwframe+0x46/0xb0"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/10cbfecc0f99f579fb170feee866c9efaab7ee47",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2be5bd42a5bba1a05daedc86cf0e248210009669",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b17294e7aa8c39dbb9c3e28e2d1983c88b94b387",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53348.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53348",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.727",
"lastModified": "2025-09-17T15:15:38.727",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix deadlock when aborting transaction during relocation with scrub\n\nBefore relocating a block group we pause scrub, then do the relocation and\nthen unpause scrub. The relocation process requires starting and committing\na transaction, and if we have a failure in the critical section of the\ntransaction commit path (transaction state >= TRANS_STATE_COMMIT_START),\nwe will deadlock if there is a paused scrub.\n\nThat results in stack traces like the following:\n\n [42.479] BTRFS info (device sdc): relocating block group 53876686848 flags metadata|raid6\n [42.936] BTRFS warning (device sdc): Skipping commit of aborted transaction.\n [42.936] ------------[ cut here ]------------\n [42.936] BTRFS: Transaction aborted (error -28)\n [42.936] WARNING: CPU: 11 PID: 346822 at fs/btrfs/transaction.c:1977 btrfs_commit_transaction+0xcc8/0xeb0 [btrfs]\n [42.936] Modules linked in: dm_flakey dm_mod loop btrfs (...)\n [42.936] CPU: 11 PID: 346822 Comm: btrfs Tainted: G W 6.3.0-rc2-btrfs-next-127+ #1\n [42.936] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n [42.936] RIP: 0010:btrfs_commit_transaction+0xcc8/0xeb0 [btrfs]\n [42.936] Code: ff ff 45 8b (...)\n [42.936] RSP: 0018:ffffb58649633b48 EFLAGS: 00010282\n [42.936] RAX: 0000000000000000 RBX: ffff8be6ef4d5bd8 RCX: 0000000000000000\n [42.936] RDX: 0000000000000002 RSI: ffffffffb35e7782 RDI: 00000000ffffffff\n [42.936] RBP: ffff8be6ef4d5c98 R08: 0000000000000000 R09: ffffb586496339e8\n [42.936] R10: 0000000000000001 R11: 0000000000000001 R12: ffff8be6d38c7c00\n [42.936] R13: 00000000ffffffe4 R14: ffff8be6c268c000 R15: ffff8be6ef4d5cf0\n [42.936] FS: 00007f381a82b340(0000) GS:ffff8beddfcc0000(0000) knlGS:0000000000000000\n [42.936] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [42.936] CR2: 00007f1e35fb7638 CR3: 0000000117680006 CR4: 0000000000370ee0\n [42.936] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n [42.936] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n [42.936] Call Trace:\n [42.936] <TASK>\n [42.936] ? start_transaction+0xcb/0x610 [btrfs]\n [42.936] prepare_to_relocate+0x111/0x1a0 [btrfs]\n [42.936] relocate_block_group+0x57/0x5d0 [btrfs]\n [42.936] ? btrfs_wait_nocow_writers+0x25/0xb0 [btrfs]\n [42.936] btrfs_relocate_block_group+0x248/0x3c0 [btrfs]\n [42.936] ? __pfx_autoremove_wake_function+0x10/0x10\n [42.936] btrfs_relocate_chunk+0x3b/0x150 [btrfs]\n [42.936] btrfs_balance+0x8ff/0x11d0 [btrfs]\n [42.936] ? __kmem_cache_alloc_node+0x14a/0x410\n [42.936] btrfs_ioctl+0x2334/0x32c0 [btrfs]\n [42.937] ? mod_objcg_state+0xd2/0x360\n [42.937] ? refill_obj_stock+0xb0/0x160\n [42.937] ? seq_release+0x25/0x30\n [42.937] ? __rseq_handle_notify_resume+0x3b5/0x4b0\n [42.937] ? percpu_counter_add_batch+0x2e/0xa0\n [42.937] ? __x64_sys_ioctl+0x88/0xc0\n [42.937] __x64_sys_ioctl+0x88/0xc0\n [42.937] do_syscall_64+0x38/0x90\n [42.937] entry_SYSCALL_64_after_hwframe+0x72/0xdc\n [42.937] RIP: 0033:0x7f381a6ffe9b\n [42.937] Code: 00 48 89 44 24 (...)\n [42.937] RSP: 002b:00007ffd45ecf060 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\n [42.937] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f381a6ffe9b\n [42.937] RDX: 00007ffd45ecf150 RSI: 00000000c4009420 RDI: 0000000000000003\n [42.937] RBP: 0000000000000003 R08: 0000000000000013 R09: 0000000000000000\n [42.937] R10: 00007f381a60c878 R11: 0000000000000246 R12: 00007ffd45ed0423\n [42.937] R13: 00007ffd45ecf150 R14: 0000000000000000 R15: 00007ffd45ecf148\n [42.937] </TASK>\n [42.937] ---[ end trace 0000000000000000 ]---\n [42.937] BTRFS: error (device sdc: state A) in cleanup_transaction:1977: errno=-28 No space left\n [59.196] INFO: task btrfs:346772 blocked for more than 120 seconds.\n [59.196] Tainted: G W 6.3.0-rc2-btrfs-next-127+ #1\n [59.196] \"echo 0 > /proc/sys/kernel/hung_\n---truncated---"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/10a5831b193390b77705fc174a309476c23ba64a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2d82a40aa7d6fcae0250ec68b8566cdee7bfd44c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6134a4bb6b1c411a244edee041ac89266c78d45c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53349.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2023-53349",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.827",
"lastModified": "2025-09-17T15:15:38.827",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ov2740: Fix memleak in ov2740_init_controls()\n\nThere is a kmemleak when testing the media/i2c/ov2740.c with bpf mock\ndevice:\n\nunreferenced object 0xffff8881090e19e0 (size 16):\n comm \"51-i2c-ov2740\", pid 278, jiffies 4294781584 (age 23.613s)\n hex dump (first 16 bytes):\n 00 f3 7c 0b 81 88 ff ff 80 75 6a 09 81 88 ff ff ..|......uj.....\n backtrace:\n [<000000004e9fad8f>] __kmalloc_node+0x44/0x1b0\n [<0000000039c802f4>] kvmalloc_node+0x34/0x180\n [<000000009b8b5c63>] v4l2_ctrl_handler_init_class+0x11d/0x180\n[videodev]\n [<0000000038644056>] ov2740_probe+0x37d/0x84f [ov2740]\n [<0000000092489f59>] i2c_device_probe+0x28d/0x680\n [<000000001038babe>] really_probe+0x17c/0x3f0\n [<0000000098c7af1c>] __driver_probe_device+0xe3/0x170\n [<00000000e1b3dc24>] device_driver_attach+0x34/0x80\n [<000000005a04a34d>] bind_store+0x10b/0x1a0\n [<00000000ce25d4f2>] drv_attr_store+0x49/0x70\n [<000000007d9f4e9a>] sysfs_kf_write+0x8c/0xb0\n [<00000000be6cff0f>] kernfs_fop_write_iter+0x216/0x2e0\n [<0000000031ddb40a>] vfs_write+0x658/0x810\n [<0000000041beecdd>] ksys_write+0xd6/0x1b0\n [<0000000023755840>] do_syscall_64+0x38/0x90\n [<00000000b2cc2da2>] entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nov2740_init_controls() won't clean all the allocated resources in fail\npath, which may causes the memleaks. Add v4l2_ctrl_handler_free() to\nprevent memleak."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d899592ed7829d0d5140853bac4d58742a6b8af",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3969b2ebc66039306f505c7c630c5530800f83c0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/7c405ee63447f14eefcfe12a18aa749abbd596ea",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a163ee11345d8322321c28bd61631de32455b987",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/fc33380ae06f438b652f66b9370b543976ac8a03",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53350.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2023-53350",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:38.943",
"lastModified": "2025-09-17T15:15:38.943",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix slicing memory leak\n\nThe temporary buffer storing slicing configuration data from user is only\nfreed on error. This is a memory leak. Free the buffer unconditionally."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d956177b7c96e62fac762a3b7da4318cde27a73",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/df45c3e46cdb41f486eecb4277fbcc4c1ffbf9be",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53351.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2023-53351",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.057",
"lastModified": "2025-09-17T15:15:39.057",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Check scheduler work queue before calling timeout handling\n\nDuring an IGT GPU reset test we see again oops despite of\ncommit 0c8c901aaaebc9 (drm/sched: Check scheduler ready before calling\ntimeout handling).\n\nIt uses ready condition whether to call drm_sched_fault which unwind\nthe TDR leads to GPU reset.\nHowever it looks the ready condition is overloaded with other meanings,\nfor example, for the following stack is related GPU reset :\n\n0 gfx_v9_0_cp_gfx_start\n1 gfx_v9_0_cp_gfx_resume\n2 gfx_v9_0_cp_resume\n3 gfx_v9_0_hw_init\n4 gfx_v9_0_resume\n5 amdgpu_device_ip_resume_phase2\n\ndoes the following:\n\t/* start the ring */\n\tgfx_v9_0_cp_gfx_start(adev);\n\tring->sched.ready = true;\n\nThe same approach is for other ASICs as well :\ngfx_v8_0_cp_gfx_resume\ngfx_v10_0_kiq_resume, etc...\n\nAs a result, our GPU reset test causes GPU fault which calls unconditionally gfx_v9_0_fault\nand then drm_sched_fault. However now it depends on whether the interrupt service routine\ndrm_sched_fault is executed after gfx_v9_0_cp_gfx_start is completed which sets the ready\nfield of the scheduler to true even for uninitialized schedulers and causes oops vs\nno fault or when ISR drm_sched_fault is completed prior gfx_v9_0_cp_gfx_start and\nNULL pointer dereference does not occur.\n\nUse the field timeout_wq to prevent oops for uninitialized schedulers.\nThe field could be initialized by the work queue of resetting the domain.\n\nv1: Corrections to commit message (Luben)"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2da5bffe9eaa5819a868e8eaaa11b3fd0f16a691",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c43a96fc00b662cef1ef0eb22d40441ce2abae8f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53352.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2023-53352",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.173",
"lastModified": "2025-09-17T15:15:39.173",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: check null pointer before accessing when swapping\n\nAdd a check to avoid null pointer dereference as below:\n\n[ 90.002283] general protection fault, probably for non-canonical\naddress 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI\n[ 90.002292] KASAN: null-ptr-deref in range\n[0x0000000000000000-0x0000000000000007]\n[ 90.002346] ? exc_general_protection+0x159/0x240\n[ 90.002352] ? asm_exc_general_protection+0x26/0x30\n[ 90.002357] ? ttm_bo_evict_swapout_allowable+0x322/0x5e0 [ttm]\n[ 90.002365] ? ttm_bo_evict_swapout_allowable+0x42e/0x5e0 [ttm]\n[ 90.002373] ttm_bo_swapout+0x134/0x7f0 [ttm]\n[ 90.002383] ? __pfx_ttm_bo_swapout+0x10/0x10 [ttm]\n[ 90.002391] ? lock_acquire+0x44d/0x4f0\n[ 90.002398] ? ttm_device_swapout+0xa5/0x260 [ttm]\n[ 90.002412] ? lock_acquired+0x355/0xa00\n[ 90.002416] ? do_raw_spin_trylock+0xb6/0x190\n[ 90.002421] ? __pfx_lock_acquired+0x10/0x10\n[ 90.002426] ? ttm_global_swapout+0x25/0x210 [ttm]\n[ 90.002442] ttm_device_swapout+0x198/0x260 [ttm]\n[ 90.002456] ? __pfx_ttm_device_swapout+0x10/0x10 [ttm]\n[ 90.002472] ttm_global_swapout+0x75/0x210 [ttm]\n[ 90.002486] ttm_tt_populate+0x187/0x3f0 [ttm]\n[ 90.002501] ttm_bo_handle_move_mem+0x437/0x590 [ttm]\n[ 90.002517] ttm_bo_validate+0x275/0x430 [ttm]\n[ 90.002530] ? __pfx_ttm_bo_validate+0x10/0x10 [ttm]\n[ 90.002544] ? kasan_save_stack+0x33/0x60\n[ 90.002550] ? kasan_set_track+0x25/0x30\n[ 90.002554] ? __kasan_kmalloc+0x8f/0xa0\n[ 90.002558] ? amdgpu_gtt_mgr_new+0x81/0x420 [amdgpu]\n[ 90.003023] ? ttm_resource_alloc+0xf6/0x220 [ttm]\n[ 90.003038] amdgpu_bo_pin_restricted+0x2dd/0x8b0 [amdgpu]\n[ 90.003210] ? __x64_sys_ioctl+0x131/0x1a0\n[ 90.003210] ? do_syscall_64+0x60/0x90"
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/1fdd16d89c01336d9a942b5f03673c17d401da87",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2dedcf414bb01b8d966eb445db1d181d92304fb2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/49b3b979e79faef129605018ad82aa0f2258f2f7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8089eb93d6787dbf348863e935698b4610d90321",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d39971d902d067b4dc366981b75b17c8c57ed5d1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53353.json
+25
View File
@@ -0,0 +1,25 @@
{
"id": "CVE-2023-53353",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.293",
"lastModified": "2025-09-17T15:15:39.293",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: postpone mem_mgr IDR destruction to hpriv_release()\n\nThe memory manager IDR is currently destroyed when user releases the\nfile descriptor.\nHowever, at this point the user context might be still held, and memory\nbuffers might be still in use.\nLater on, calls to release those buffers will fail due to not finding\ntheir handles in the IDR, leading to a memory leak.\nTo avoid this leak, split the IDR destruction from the memory manager\nfini, and postpone it to hpriv_release() when there is no user context\nand no buffers are used."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2e8e9a895c4589f124a37fc84d123b5114406e94",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/840de329ca99cafd0cdde9c6ac160b1330942aba",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53354.json
+49
View File
@@ -0,0 +1,49 @@
{
"id": "CVE-2023-53354",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.403",
"lastModified": "2025-09-17T15:15:39.403",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskbuff: skb_segment, Call zero copy functions before using skbuff frags\n\nCommit bf5c25d60861 (\"skbuff: in skb_segment, call zerocopy functions\nonce per nskb\") added the call to zero copy functions in skb_segment().\nThe change introduced a bug in skb_segment() because skb_orphan_frags()\nmay possibly change the number of fragments or allocate new fragments\naltogether leaving nrfrags and frag to point to the old values. This can\ncause a panic with stacktrace like the one below.\n\n[ 193.894380] BUG: kernel NULL pointer dereference, address: 00000000000000bc\n[ 193.895273] CPU: 13 PID: 18164 Comm: vh-net-17428 Kdump: loaded Tainted: G O 5.15.123+ #26\n[ 193.903919] RIP: 0010:skb_segment+0xb0e/0x12f0\n[ 194.021892] Call Trace:\n[ 194.027422] <TASK>\n[ 194.072861] tcp_gso_segment+0x107/0x540\n[ 194.082031] inet_gso_segment+0x15c/0x3d0\n[ 194.090783] skb_mac_gso_segment+0x9f/0x110\n[ 194.095016] __skb_gso_segment+0xc1/0x190\n[ 194.103131] netem_enqueue+0x290/0xb10 [sch_netem]\n[ 194.107071] dev_qdisc_enqueue+0x16/0x70\n[ 194.110884] __dev_queue_xmit+0x63b/0xb30\n[ 194.121670] bond_start_xmit+0x159/0x380 [bonding]\n[ 194.128506] dev_hard_start_xmit+0xc3/0x1e0\n[ 194.131787] __dev_queue_xmit+0x8a0/0xb30\n[ 194.138225] macvlan_start_xmit+0x4f/0x100 [macvlan]\n[ 194.141477] dev_hard_start_xmit+0xc3/0x1e0\n[ 194.144622] sch_direct_xmit+0xe3/0x280\n[ 194.147748] __dev_queue_xmit+0x54a/0xb30\n[ 194.154131] tap_get_user+0x2a8/0x9c0 [tap]\n[ 194.157358] tap_sendmsg+0x52/0x8e0 [tap]\n[ 194.167049] handle_tx_zerocopy+0x14e/0x4c0 [vhost_net]\n[ 194.173631] handle_tx+0xcd/0xe0 [vhost_net]\n[ 194.176959] vhost_worker+0x76/0xb0 [vhost]\n[ 194.183667] kthread+0x118/0x140\n[ 194.190358] ret_from_fork+0x1f/0x30\n[ 194.193670] </TASK>\n\nIn this case calling skb_orphan_frags() updated nr_frags leaving nrfrags\nlocal variable in skb_segment() stale. This resulted in the code hitting\ni >= nrfrags prematurely and trying to move to next frag_skb using\nlist_skb pointer, which was NULL, and caused kernel panic. Move the call\nto zero copy functions before using frags and nr_frags."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/04c3eee4e13f60bf6f9a366ad39f88a01a57166e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2ea35288c83b3d501a88bc17f2df8f176b5cc96f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6c26ed3c6abe86ddab0510529000b970b05c9b40",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8836c266201c29a5acb4f582227686f47b65ad61",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d44403ec0676317b7f7edf2a035bb219fee3304e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d5790386595d06ea9decfd9ba5f1ea48cf09aa02",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f99006e840a4dbc8f5a34cecc6b5b26c73ef49bb",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/fcab3f661dbfd88e27ddbbe65368f3fa2d823175",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53355.json
+29
View File
@@ -0,0 +1,29 @@
{
"id": "CVE-2023-53355",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.523",
"lastModified": "2025-09-17T15:15:39.523",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: pi433: fix memory leak with using debugfs_lookup()\n\nWhen calling debugfs_lookup() the result must have dput() called on it,\notherwise the memory will leak over time. To make things simpler, just\ncall debugfs_lookup_and_remove() instead which handles all of the logic\nat once. This requires saving off the root directory dentry to make\ncreation of individual device subdirectories easier."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/04f3cda40e9f6653ae15ed3fcf26ef2860f4df66",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2f36e789e540df6a9fbf471b3a2ba62a8b361586",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bb16f3102607b69e1a0233f4b73c6e337f86ef8d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53356.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2023-53356",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.640",
"lastModified": "2025-09-17T15:15:39.640",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: u_serial: Add null pointer check in gserial_suspend\n\nConsider a case where gserial_disconnect has already cleared\ngser->ioport. And if gserial_suspend gets called afterwards,\nit will lead to accessing of gser->ioport and thus causing\nnull pointer dereference.\n\nAvoid this by adding a null pointer check. Added a static\nspinlock to prevent gser->ioport from becoming null after\nthe newly added null pointer check."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/2788a3553f7497075653210b42e2aeb6ba95e28e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/2f6ecb89fe8feb2b60a53325b0eeb9866d88909a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/374447e3367767156405bedd230c5d391f4b7962",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a8ea7ed644cbf6314b5b0136b5398754b549fb8f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e60a827ac074ce6bd58305fe5a86afab5fce6a04",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53357.json
+49
View File
@@ -0,0 +1,49 @@
{
"id": "CVE-2023-53357",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.763",
"lastModified": "2025-09-17T15:15:39.763",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid10: check slab-out-of-bounds in md_bitmap_get_counter\n\nIf we write a large number to md/bitmap_set_bits, md_bitmap_checkpage()\nwill return -EINVAL because 'page >= bitmap->pages', but the return value\nwas not checked immediately in md_bitmap_get_counter() in order to set\n*blocks value and slab-out-of-bounds occurs.\n\nMove check of 'page >= bitmap->pages' to md_bitmap_get_counter() and\nreturn directly if true."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/152bb26796ff054af50b2ee1b3ca56e364e4f61b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/301867b1c16805aebbc306aafa6ecdc68b73c7e5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/374fb914304d9b500721007f3837ea8f1f9a2418",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/39fa14e824acfd470db4f42c354297456bd82b53",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a134dd582c0d5b6068efa308bd485cf1d00b3f65",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b0b971fe7d61411ede63c3291764dbde1577ef2c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/be1a3ec63a840cc9e59a033acf154f56255699a1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bea301c046110bf421a3ce153fb868cb8d618e90",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53358.json
+37
View File
@@ -0,0 +1,37 @@
{
"id": "CVE-2023-53358",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:39.890",
"lastModified": "2025-09-17T15:15:39.890",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix racy issue under cocurrent smb2 tree disconnect\n\nThere is UAF issue under cocurrent smb2 tree disconnect.\nThis patch introduce TREE_CONN_EXPIRE flags for tcon to avoid cocurrent\naccess."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/30210947a343b6b3ca13adc9bfc88e1543e16dd5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/39366b47a59d46af15ac57beb0996268bf911f6a",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b36295c17fb97424406f0c3ab321b1ccaabb9be8",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/bd80d35725a0cf4df9307bfe2f1a3b2cb983d8e6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/dc1c17716c099c90948ebb83e2170dd75a3be6b6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53359.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2023-53359",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:40.010",
"lastModified": "2025-09-17T15:15:40.010",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: fix memory leak with using debugfs_lookup()\n\nWhen calling debugfs_lookup() the result must have dput() called on it,\notherwise the memory will leak over time. To make things simpler, just\ncall debugfs_lookup_and_remove() instead which handles all of the logic at\nonce."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/30374434edab20e25776f8ecb4bc9d1e54309487",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6683327b51a601daba32900072349dfa1d4e8fea",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c68ece7baf2aa9783b8244482c03010d477d4a93",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/cc00340fb1226a2a3a5cf15473ac417da3c952f1",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53360.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2023-53360",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:40.123",
"lastModified": "2025-09-17T15:15:40.123",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4.2: Rework scratch handling for READ_PLUS (again)\n\nI found that the read code might send multiple requests using the same\nnfs_pgio_header, but nfs4_proc_read_setup() is only called once. This is\nhow we ended up occasionally double-freeing the scratch buffer, but also\nmeans we set a NULL pointer but non-zero length to the xdr scratch\nbuffer. This results in an oops the first time decoding needs to copy\nsomething to scratch, which frequently happens when decoding READ_PLUS\nhole segments.\n\nI fix this by moving scratch handling into the pageio read code. I\nprovide a function to allocate scratch space for decoding read replies,\nand free the scratch buffer when the nfs_pgio_header is freed."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/303a78052091c81e9003915c521fdca1c7e117af",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a2f4cb206bd94b3f4a7bb05fcdce9525283b5681",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/adac9f0ddd2b291c7ce41f549fdb27a13616cff5",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ae5d5672f1db711e91db6f52df5cb16ecd8f5692",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
CVE-2023/CVE-2023-533xx/CVE-2023-53361.json
+33
View File
@@ -0,0 +1,33 @@
{
"id": "CVE-2023-53361",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2025-09-17T15:15:40.247",
"lastModified": "2025-09-17T15:15:40.247",
"vulnStatus": "Received",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: mm: Add p?d_leaf() definitions\n\nWhen I do LTP test, LTP test case ksm06 caused panic at\n\tbreak_ksm_pmd_entry\n\t -> pmd_leaf (Huge page table but False)\n\t -> pte_present (panic)\n\nThe reason is pmd_leaf() is not defined, So like commit 501b81046701\n(\"mips: mm: add p?d_leaf() definitions\") add p?d_leaf() definition for\nLoongArch."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/303be4b33562a5b689261ced1616bf16ad49efa7",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/593ad636bac41d67bdc44c83c6945015471313fc",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/77aaf22a9200b9557793c96debead911b80acc1c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/cc9bf2d62f196ec600f9e6ea3a6ced11f54a2df9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}
Loaded 100 of 340 files, more files were not shown because too many files have changed in this diff. Show more