CVE-2022-49979 (GCVE-0-2022-49979)
Vulnerability from cvelistv5
Published
2025-06-18 11:00
Modified
2026-10-15 21:31
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: fix refcount bug in sk_psock_get (2)
Syzkaller reports refcount bug as follows:
------------[ cut here ]------------
refcount_t: saturated; leaking memory.
WARNING: CPU: 1 PID: 3605 at lib/refcount.c:19 refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19
Modules linked in:
CPU: 1 PID: 3605 Comm: syz-executor208 Not tainted 5.18.0-syzkaller-03023-g7e062cda7d90 #0
<TASK>
__refcount_add_not_zero include/linux/refcount.h:163 [inline]
__refcount_inc_not_zero include/linux/refcount.h:227 [inline]
refcount_inc_not_zero include/linux/refcount.h:245 [inline]
sk_psock_get+0x3bc/0x410 include/linux/skmsg.h:439
tls_data_ready+0x6d/0x1b0 net/tls/tls_sw.c:2091
tcp_data_ready+0x106/0x520 net/ipv4/tcp_input.c:4983
tcp_data_queue+0x25f2/0x4c90 net/ipv4/tcp_input.c:5057
tcp_rcv_state_process+0x1774/0x4e80 net/ipv4/tcp_input.c:6659
tcp_v4_do_rcv+0x339/0x980 net/ipv4/tcp_ipv4.c:1682
sk_backlog_rcv include/net/sock.h:1061 [inline]
__release_sock+0x134/0x3b0 net/core/sock.c:2849
release_sock+0x54/0x1b0 net/core/sock.c:3404
inet_shutdown+0x1e0/0x430 net/ipv4/af_inet.c:909
__sys_shutdown_sock net/socket.c:2331 [inline]
__sys_shutdown_sock net/socket.c:2325 [inline]
__sys_shutdown+0xf1/0x1b0 net/socket.c:2343
__do_sys_shutdown net/socket.c:2351 [inline]
__se_sys_shutdown net/socket.c:2349 [inline]
__x64_sys_shutdown+0x50/0x70 net/socket.c:2349
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x46/0xb0
</TASK>
During SMC fallback process in connect syscall, kernel will
replaces TCP with SMC. In order to forward wakeup
smc socket waitqueue after fallback, kernel will sets
clcsk->sk_user_data to origin smc socket in
smc_fback_replace_callbacks().
Later, in shutdown syscall, kernel will calls
sk_psock_get(), which treats the clcsk->sk_user_data
as psock type, triggering the refcnt warning.
So, the root cause is that smc and psock, both will use
sk_user_data field. So they will mismatch this field
easily.
This patch solves it by using another bit(defined as
SK_USER_DATA_PSOCK) in PTRMASK, to mark whether
sk_user_data points to a psock object or not.
This patch depends on a PTRMASK introduced in commit f1ff5ce2cd5e
("net, sk_msg: Clear sk_user_data pointer on clone if tagged").
For there will possibly be more flags in the sk_user_data field,
this patch also refactor sk_user_data flags code to be more generic
to improve its maintainability.
References
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2022-49979",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-15T21:29:58.983226Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-15T21:31:18.017Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/linux/skmsg.h",
"include/net/sock.h",
"net/core/skmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a5d1cb908131e939bd8b63b8e5e23365bbc2edaf",
"status": "affected",
"version": "0ef6049f664941bc0f75828b3a61877635048b27",
"versionType": "git"
},
{
"lessThan": "86026be8535c16fcc5e4f960286faf04d7f77815",
"status": "affected",
"version": "341adeec9adad0874f29a0a1af35638207352a39",
"versionType": "git"
},
{
"lessThan": "2a0133723f9ebeb751cfce19f74ec07e108bef1f",
"status": "affected",
"version": "341adeec9adad0874f29a0a1af35638207352a39",
"versionType": "git"
},
{
"status": "affected",
"version": "504078fbe9dd570d685361b57784a6050bc40aaa",
"versionType": "git"
},
{
"lessThan": "5.15.65",
"status": "affected",
"version": "5.15.22",
"versionType": "semver"
},
{
"lessThan": "5.17",
"status": "affected",
"version": "5.16.8",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/linux/skmsg.h",
"include/net/sock.h",
"net/core/skmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.17"
},
{
"lessThan": "5.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.65",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.19.*",
"status": "unaffected",
"version": "5.19.7",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.65",
"versionStartIncluding": "5.15.22",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.19.7",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.0",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.16.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix refcount bug in sk_psock_get (2)\n\nSyzkaller reports refcount bug as follows:\n------------[ cut here ]------------\nrefcount_t: saturated; leaking memory.\nWARNING: CPU: 1 PID: 3605 at lib/refcount.c:19 refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19\nModules linked in:\nCPU: 1 PID: 3605 Comm: syz-executor208 Not tainted 5.18.0-syzkaller-03023-g7e062cda7d90 #0\n \u003cTASK\u003e\n __refcount_add_not_zero include/linux/refcount.h:163 [inline]\n __refcount_inc_not_zero include/linux/refcount.h:227 [inline]\n refcount_inc_not_zero include/linux/refcount.h:245 [inline]\n sk_psock_get+0x3bc/0x410 include/linux/skmsg.h:439\n tls_data_ready+0x6d/0x1b0 net/tls/tls_sw.c:2091\n tcp_data_ready+0x106/0x520 net/ipv4/tcp_input.c:4983\n tcp_data_queue+0x25f2/0x4c90 net/ipv4/tcp_input.c:5057\n tcp_rcv_state_process+0x1774/0x4e80 net/ipv4/tcp_input.c:6659\n tcp_v4_do_rcv+0x339/0x980 net/ipv4/tcp_ipv4.c:1682\n sk_backlog_rcv include/net/sock.h:1061 [inline]\n __release_sock+0x134/0x3b0 net/core/sock.c:2849\n release_sock+0x54/0x1b0 net/core/sock.c:3404\n inet_shutdown+0x1e0/0x430 net/ipv4/af_inet.c:909\n __sys_shutdown_sock net/socket.c:2331 [inline]\n __sys_shutdown_sock net/socket.c:2325 [inline]\n __sys_shutdown+0xf1/0x1b0 net/socket.c:2343\n __do_sys_shutdown net/socket.c:2351 [inline]\n __se_sys_shutdown net/socket.c:2349 [inline]\n __x64_sys_shutdown+0x50/0x70 net/socket.c:2349\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x46/0xb0\n \u003c/TASK\u003e\n\nDuring SMC fallback process in connect syscall, kernel will\nreplaces TCP with SMC. In order to forward wakeup\nsmc socket waitqueue after fallback, kernel will sets\nclcsk-\u003esk_user_data to origin smc socket in\nsmc_fback_replace_callbacks().\n\nLater, in shutdown syscall, kernel will calls\nsk_psock_get(), which treats the clcsk-\u003esk_user_data\nas psock type, triggering the refcnt warning.\n\nSo, the root cause is that smc and psock, both will use\nsk_user_data field. So they will mismatch this field\neasily.\n\nThis patch solves it by using another bit(defined as\nSK_USER_DATA_PSOCK) in PTRMASK, to mark whether\nsk_user_data points to a psock object or not.\nThis patch depends on a PTRMASK introduced in commit f1ff5ce2cd5e\n(\"net, sk_msg: Clear sk_user_data pointer on clone if tagged\").\n\nFor there will possibly be more flags in the sk_user_data field,\nthis patch also refactor sk_user_data flags code to be more generic\nto improve its maintainability."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - Exploitation requires local syscalls: create an AF_SMC socket, connect to trigger fallback (storing smc_sock in sk_user_data), enable kTLS via setsockopt, then shutdown/recv. Remote packets alone cannot establish this confused socket state.\nAC:L - The attacker fully controls the setup sequence (SMC connect fallback, TCP_ULP/TLS_RX, shutdown); no race or external timing is required. SMC is autoloadable via socket(AF_SMC) and kTLS is commonly available as a loaded/built-in module.\nPR:L - An unprivileged local user can create AF_SMC sockets, trigger fallback to a normal TCP peer, and set TCP_ULP/\"tls\" plus TLS_RX on their own socket with no capabilities required once the TLS module is present.\nUI:N - The attacker performs connect, setsockopt, and shutdown on their own sockets; no victim interaction is needed.\nS:U - Impact is confined to the local kernel\u0027s network stack authority (corruption/UAF of kernel socket objects); this is standard privilege escalation scope, not a VM/host boundary crossing.\nC:H - Type confusion treats a live smc_sock as sk_psock, reading sock fields as list heads and enabling a path to sk_psock_drop/kfree of the wrong object\u2014UAF-class memory corruption that can be leveraged for arbitrary kernel read primitives.\nI:H - sk_psock_get performs refcount_inc_not_zero at a fixed offset into the smc_sock\u0027s embedded struct sock, and a successful get/put path can invoke sk_psock_drop (function-pointer misuse and kfree of the SMC object), yielding write/UAF primitives and potential control-flow hijack.\nA:H - The bug triggers refcount saturation WARNINGs and can oops/panic via bad pointer interpretation or UAF when the misaligned field permits sk_psock_drop, reliably impacting kernel availability."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T08:57:00.093Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/a5d1cb908131e939bd8b63b8e5e23365bbc2edaf"
},
{
"url": "https://git.kernel.org/stable/c/86026be8535c16fcc5e4f960286faf04d7f77815"
},
{
"url": "https://git.kernel.org/stable/c/2a0133723f9ebeb751cfce19f74ec07e108bef1f"
}
],
"title": "net: fix refcount bug in sk_psock_get (2)",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2022-49979",
"datePublished": "2025-06-18T11:00:41.513Z",
"dateReserved": "2025-06-18T10:57:27.385Z",
"dateUpdated": "2026-10-15T21:31:18.017Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-49979\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-15T21:29:58.983226Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-15T21:29:59.532Z\"}}], \"cna\": {\"title\": \"net: fix refcount bug in sk_psock_get (2)\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.8, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - Exploitation requires local syscalls: create an AF_SMC socket, connect to trigger fallback (storing smc_sock in sk_user_data), enable kTLS via setsockopt, then shutdown/recv. Remote packets alone cannot establish this confused socket state.\\nAC:L - The attacker fully controls the setup sequence (SMC connect fallback, TCP_ULP/TLS_RX, shutdown); no race or external timing is required. SMC is autoloadable via socket(AF_SMC) and kTLS is commonly available as a loaded/built-in module.\\nPR:L - An unprivileged local user can create AF_SMC sockets, trigger fallback to a normal TCP peer, and set TCP_ULP/\\\"tls\\\" plus TLS_RX on their own socket with no capabilities required once the TLS module is present.\\nUI:N - The attacker performs connect, setsockopt, and shutdown on their own sockets; no victim interaction is needed.\\nS:U - Impact is confined to the local kernel\u0027s network stack authority (corruption/UAF of kernel socket objects); this is standard privilege escalation scope, not a VM/host boundary crossing.\\nC:H - Type confusion treats a live smc_sock as sk_psock, reading sock fields as list heads and enabling a path to sk_psock_drop/kfree of the wrong object\\u2014UAF-class memory corruption that can be leveraged for arbitrary kernel read primitives.\\nI:H - sk_psock_get performs refcount_inc_not_zero at a fixed offset into the smc_sock\u0027s embedded struct sock, and a successful get/put path can invoke sk_psock_drop (function-pointer misuse and kfree of the SMC object), yielding write/UAF primitives and potential control-flow hijack.\\nA:H - The bug triggers refcount saturation WARNINGs and can oops/panic via bad pointer interpretation or UAF when the misaligned field permits sk_psock_drop, reliably impacting kernel availability.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"0ef6049f664941bc0f75828b3a61877635048b27\", \"lessThan\": \"a5d1cb908131e939bd8b63b8e5e23365bbc2edaf\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"341adeec9adad0874f29a0a1af35638207352a39\", \"lessThan\": \"86026be8535c16fcc5e4f960286faf04d7f77815\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"341adeec9adad0874f29a0a1af35638207352a39\", \"lessThan\": \"2a0133723f9ebeb751cfce19f74ec07e108bef1f\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"504078fbe9dd570d685361b57784a6050bc40aaa\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"5.15.22\", \"lessThan\": \"5.15.65\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"5.16.8\", \"lessThan\": \"5.17\", \"versionType\": \"semver\"}], \"programFiles\": [\"include/linux/skmsg.h\", \"include/net/sock.h\", \"net/core/skmsg.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.17\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.17\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.65\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.19.7\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.19.*\"}, {\"status\": \"unaffected\", \"version\": \"6.0\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"include/linux/skmsg.h\", \"include/net/sock.h\", \"net/core/skmsg.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/a5d1cb908131e939bd8b63b8e5e23365bbc2edaf\"}, {\"url\": \"https://git.kernel.org/stable/c/86026be8535c16fcc5e4f960286faf04d7f77815\"}, {\"url\": \"https://git.kernel.org/stable/c/2a0133723f9ebeb751cfce19f74ec07e108bef1f\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: fix refcount bug in sk_psock_get (2)\\n\\nSyzkaller reports refcount bug as follows:\\n------------[ cut here ]------------\\nrefcount_t: saturated; leaking memory.\\nWARNING: CPU: 1 PID: 3605 at lib/refcount.c:19 refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19\\nModules linked in:\\nCPU: 1 PID: 3605 Comm: syz-executor208 Not tainted 5.18.0-syzkaller-03023-g7e062cda7d90 #0\\n \u003cTASK\u003e\\n __refcount_add_not_zero include/linux/refcount.h:163 [inline]\\n __refcount_inc_not_zero include/linux/refcount.h:227 [inline]\\n refcount_inc_not_zero include/linux/refcount.h:245 [inline]\\n sk_psock_get+0x3bc/0x410 include/linux/skmsg.h:439\\n tls_data_ready+0x6d/0x1b0 net/tls/tls_sw.c:2091\\n tcp_data_ready+0x106/0x520 net/ipv4/tcp_input.c:4983\\n tcp_data_queue+0x25f2/0x4c90 net/ipv4/tcp_input.c:5057\\n tcp_rcv_state_process+0x1774/0x4e80 net/ipv4/tcp_input.c:6659\\n tcp_v4_do_rcv+0x339/0x980 net/ipv4/tcp_ipv4.c:1682\\n sk_backlog_rcv include/net/sock.h:1061 [inline]\\n __release_sock+0x134/0x3b0 net/core/sock.c:2849\\n release_sock+0x54/0x1b0 net/core/sock.c:3404\\n inet_shutdown+0x1e0/0x430 net/ipv4/af_inet.c:909\\n __sys_shutdown_sock net/socket.c:2331 [inline]\\n __sys_shutdown_sock net/socket.c:2325 [inline]\\n __sys_shutdown+0xf1/0x1b0 net/socket.c:2343\\n __do_sys_shutdown net/socket.c:2351 [inline]\\n __se_sys_shutdown net/socket.c:2349 [inline]\\n __x64_sys_shutdown+0x50/0x70 net/socket.c:2349\\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\\n do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\\n entry_SYSCALL_64_after_hwframe+0x46/0xb0\\n \u003c/TASK\u003e\\n\\nDuring SMC fallback process in connect syscall, kernel will\\nreplaces TCP with SMC. In order to forward wakeup\\nsmc socket waitqueue after fallback, kernel will sets\\nclcsk-\u003esk_user_data to origin smc socket in\\nsmc_fback_replace_callbacks().\\n\\nLater, in shutdown syscall, kernel will calls\\nsk_psock_get(), which treats the clcsk-\u003esk_user_data\\nas psock type, triggering the refcnt warning.\\n\\nSo, the root cause is that smc and psock, both will use\\nsk_user_data field. So they will mismatch this field\\neasily.\\n\\nThis patch solves it by using another bit(defined as\\nSK_USER_DATA_PSOCK) in PTRMASK, to mark whether\\nsk_user_data points to a psock object or not.\\nThis patch depends on a PTRMASK introduced in commit f1ff5ce2cd5e\\n(\\\"net, sk_msg: Clear sk_user_data pointer on clone if tagged\\\").\\n\\nFor there will possibly be more flags in the sk_user_data field,\\nthis patch also refactor sk_user_data flags code to be more generic\\nto improve its maintainability.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.65\", \"versionStartIncluding\": \"5.15.22\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.19.7\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.0\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"5.16.8\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T08:57:00.093Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2022-49979\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-15T21:31:18.017Z\", \"dateReserved\": \"2025-06-18T10:57:27.385Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2025-06-18T11:00:41.513Z\", \"assignerShortName\": \"Linux\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…