FKIE_CVE-2026-90221
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-10-19 09:19| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/nfc/nci/rsp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "baed3fdf6ed2195c56f25ae18a086b938dcd3983",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "2f434478771a4ebdd535033561c0590bcde39753",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "bbe68e8249e2c76d65adfd9224fa95f1ca0fbe4e",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "4f0483bbcdaccc9d4aee30df7351863334cecfa7",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "7d44b897bff84edcd4814899314d661ad4956a8e",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
},
{
"lessThan": "d56575a2595ee1f597f39e8a1cfb67ed3501678d",
"status": "affected",
"version": "bcd684aace34fedbd473fbd9b21ed06b0c2d2212",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/nfc/nci/rsp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.11"
},
{
"lessThan": "5.11",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.221",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing\n\nnci_core_init_rsp_packet_v1() and nci_core_init_rsp_packet_v2() parse\nthe CORE_INIT_RSP packet without validating that the skb contains\nenough data. A malformed response (e.g. injected via virtual_ncidev)\ncan declare a large num_supported_rf_interfaces while providing\ninsufficient data, causing reads of uninitialized slab memory. This\nis later used in nci_init_complete_req(), triggering a KMSAN\nuninit-value warning.\n\nAdd skb length checks before accessing packet fields:\n- Validate the skb has at least 1 byte for the status field.\n- Validate the skb can hold the fixed-size header before parsing.\n- In v2, bounds-check each variable-length rf_interface entry and its\n extension parameters within the parsing loop.\n- In v1, verify the skb is large enough for both the variable-length\n rf_interfaces array and the trailing rsp_2 structure."
}
],
"id": "CVE-2026-90221",
"lastModified": "2026-10-19T09:19:12.287",
"metrics": {},
"published": "2026-09-17T17:17:17.550",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2f434478771a4ebdd535033561c0590bcde39753"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4f0483bbcdaccc9d4aee30df7351863334cecfa7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5487f04c1ccbfa15aa6e531eb1ec9c9ec9c7bf31"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7d44b897bff84edcd4814899314d661ad4956a8e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/baed3fdf6ed2195c56f25ae18a086b938dcd3983"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bbe68e8249e2c76d65adfd9224fa95f1ca0fbe4e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d56575a2595ee1f597f39e8a1cfb67ed3501678d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.