193 lines
10 KiB
JSON
193 lines
10 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2024-49999",
|
|
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "Linux",
|
|
"dateReserved": "2024-10-21T12:17:06.057Z",
|
|
"datePublished": "2024-10-21T18:02:38.958Z",
|
|
"dateUpdated": "2026-08-05T11:41:00.098Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"shortName": "Linux",
|
|
"dateUpdated": "2026-08-05T11:41:00.098Z"
|
|
},
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Fix the setting of the server responding flag\n\nIn afs_wait_for_operation(), we set transcribe the call responded flag to\nthe server record that we used after doing the fileserver iteration loop -\nbut it's possible to exit the loop having had a response from the server\nthat we've discarded (e.g. it returned an abort or we started receiving\ndata, but the call didn't complete).\n\nThis means that op->server might be NULL, but we don't check that before\nattempting to set the server flag."
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
|
"baseScore": 7.5,
|
|
"baseSeverity": "HIGH"
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "AV:N - The vulnerable code is in the kAFS network filesystem client and is driven entirely by responses received from remote AFS fileservers and VL servers over RxRPC/UDP; a malicious/compromised fileserver in the cell, or an on-path attacker spoofing the unauthenticated (rxnull, the default for anonymous access) RxRPC abort/response packets, reaches it across the network.\nAC:L - No local access or adjacency is required — AFS cells are routinely accessed over routed/internet paths. The attacker controls both halves of the condition: it makes the call \"respond\" (return a VMOVED/other abort, or start data then stall) and then makes the subsequent volume-status/VL step fail so the rotation loop exits at `failed:` with `op->server` already NULLed by `restart_from_beginning`. This is deterministic and can be repeated at will, requiring no memory-layout or timing luck.\nPR:N - The attacker needs no account or credentials on the victim system; it acts purely as a network peer, and kAFS talks to fileservers anonymously by default (no kerberos key required for the affected RPC/abort handling).\nUI:N - On an AFS-using host /afs is mounted at boot, and RPCs that traverse afs_wait_for_operation() are issued continuously by background writeback, callback-driven revalidation, and periodic volume-record updates from kworkers — no victim action is needed for the malicious server response to be processed.\nS:U - The faulting write and its consequences are confined to the kernel of the affected host; no VM, IOMMU, or sandbox boundary is crossed.\nC:N - The defect is a NULL-pointer write (set_bit at a fixed small offset within struct afs_server); nothing is read from or leaked out of kernel memory.\nI:N - The only write targets a fixed low address in the unmapped zero page with attacker-uncontrolled content (bit 0), so it faults rather than modifying any kernel data; no integrity impact results.\nA:H - It is a kernel oops (panic with panic_on_oops), and because the fault occurs before afs_end_vnode_operation()/afs_drop_io_locks() the dying task leaks vnode->io_lock mutexes, leaving the AFS mount permanently wedged with unkillable D-state waiters; a remote attacker can trigger it repeatedly."
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"affected": [
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "unaffected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"fs/afs/fs_operation.c"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "98f9fda2057ba34b720c4d353351024d6dcee90f",
|
|
"lessThan": "3d51ab44123f35dd1d646d99a15ebef10f55e263",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
},
|
|
{
|
|
"version": "98f9fda2057ba34b720c4d353351024d6dcee90f",
|
|
"lessThan": "97c953572d98080c5f1486155350bb688041747a",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
},
|
|
{
|
|
"version": "98f9fda2057ba34b720c4d353351024d6dcee90f",
|
|
"lessThan": "ff98751bae40faed1ba9c6a7287e84430f7dec64",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "affected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"fs/afs/fs_operation.c"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "6.8",
|
|
"status": "affected"
|
|
},
|
|
{
|
|
"version": "0",
|
|
"lessThan": "6.8",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.10.14",
|
|
"lessThanOrEqual": "6.10.*",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.11.3",
|
|
"lessThanOrEqual": "6.11.*",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.12",
|
|
"lessThanOrEqual": "*",
|
|
"status": "unaffected",
|
|
"versionType": "original_commit_for_fix"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"cpeApplicability": [
|
|
{
|
|
"nodes": [
|
|
{
|
|
"operator": "OR",
|
|
"negate": false,
|
|
"cpeMatch": [
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "6.8",
|
|
"versionEndExcluding": "6.10.14"
|
|
},
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "6.8",
|
|
"versionEndExcluding": "6.11.3"
|
|
},
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "6.8",
|
|
"versionEndExcluding": "6.12"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/3d51ab44123f35dd1d646d99a15ebef10f55e263"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/97c953572d98080c5f1486155350bb688041747a"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/ff98751bae40faed1ba9c6a7287e84430f7dec64"
|
|
}
|
|
],
|
|
"title": "afs: Fix the setting of the server responding flag",
|
|
"x_generator": {
|
|
"engine": "bippy-1.2.0"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"metrics": [
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"id": "CVE-2024-49999",
|
|
"role": "CISA Coordinator",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "no"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"version": "2.0.3",
|
|
"timestamp": "2024-10-22T13:30:13.693852Z"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2024-10-22T13:38:41.400Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |