GHSA-68MJ-7VM5-9GJG
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()
frame->ccid.datalen is read directly from the USB response frame and used, unchecked, as an index into frame->data[]. A malicious or malfunctioning device can set this field to an arbitrary value, causing the driver to read far outside the received buffer.
Bound ccid.datalen against the maximum possible ACR122 frame size before using it. This replaces the existing datalen == 0 check, since datalen < 2 already covers that case and additionally rejects datalen == 1, which would still underflow the "datalen - 2" offset used below.
{
"affected": [],
"aliases": [
"CVE-2026-98575"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()\n\nframe-\u003eccid.datalen is read directly from the USB response frame\nand used, unchecked, as an index into frame-\u003edata[]. A malicious or\nmalfunctioning device can set this field to an arbitrary value,\ncausing the driver to read far outside the received buffer.\n\nBound ccid.datalen against the maximum possible ACR122 frame size\nbefore using it. This replaces the existing datalen == 0 check,\nsince datalen \u003c 2 already covers that case and additionally\nrejects datalen == 1, which would still underflow the\n\"datalen - 2\" offset used below.",
"id": "GHSA-68mj-7vm5-9gjg",
"modified": "2026-10-18T18:31:54Z",
"published": "2026-10-18T18:31:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98575"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2450a388367231fb7dd798538f393af227c00c4d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/72b8b2126e854d6756a1aa4bdc66d7457b832294"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/74b3fbc60907ee97e3af3249091f57351b53a6d6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8a0f1bb790d964893db7fc59febda9a534db07b3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8db3b1e012a8b25078dfa1efabe3d0cd2916dcba"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b61732f47316d45f27706db7812950145d3327b5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e72cbedc4596e808d22dd2b9fff666ece76f8dd6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ea82b7576793219fa10a8b545f8338998b2a9ce2"
}
],
"schema_version": "1.4.0",
"severity": []
}
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
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.