CVE-2026-99581 (GCVE-0-2026-99581)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
e4ee0bb077cd7d70207647a0106f6ea6a74c2636 , < 4de4a28e514ea2cf9a91d198b66cda7f02ad5edb
(git)
Affected: e4ee0bb077cd7d70207647a0106f6ea6a74c2636 , < ca75b38b1a3c2eabe81d231dae4ea180cf6287cd (git) |
guessed | |
| Linux | Linux |
Affected:
6.19
Unaffected: 0 , < 6.19 (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/chrome/cros_usbpd_notify.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "4de4a28e514ea2cf9a91d198b66cda7f02ad5edb",
"status": "affected",
"version": "e4ee0bb077cd7d70207647a0106f6ea6a74c2636",
"versionType": "git"
},
{
"lessThan": "ca75b38b1a3c2eabe81d231dae4ea180cf6287cd",
"status": "affected",
"version": "e4ee0bb077cd7d70207647a0106f6ea6a74c2636",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/chrome/cros_usbpd_notify.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "6.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004\n\ncros_usbpd_notify_probe_acpi() takes the EC device pointer from\ndev_get_drvdata(dev-\u003eparent) and assumes it is a struct cros_ec_device.\nThat only holds when GOOG0003 is a child of GOOG0004. On older devices\nwithout that hierarchy, such as Google Nami, GOOG0003 and GOOG0004 are\nsiblings under the ACPI EC (PNP0C09):\n\n PNP0C09:00 (acpi-ec)\n |-- GOOG0003:00 (cros-usbpd-notify-acpi)\n `-- GOOG0004:00 (cros_ec_lpcs)\n\nBefore commit db65a06d10b3 (\"ACPI: EC: Convert the driver to a platform\none\") the parent platform device had no driver data, so the driver\nwarned and continued without an EC pointer, as intended for these\ndevices. Since that commit the ACPI EC driver stores its struct acpi_ec\nthere, so the driver treats a struct acpi_ec as a struct cros_ec_device\nand calls cros_ec_cmd() on it for every USB-C PD host event. Plugging\nor unplugging a charger then intermittently oopses, followed by soft\nlockups and a hung system:\n\n BUG: unable to handle page fault for address: ffffffff9cf03220\n #PF: supervisor write access in kernel mode\n Hardware name: Google Nami/Nami, BIOS 09/19/2019\n Workqueue: kacpi_notify acpi_os_execute_deferred\n RIP: 0010:native_queued_spin_lock_slowpath+0x29d/0x330\n Call Trace:\n _raw_spin_lock_irqsave+0x59/0x80\n __mutex_lock.constprop.0+0x129/0x930\n cros_ec_cmd_xfer+0x2a/0xf0 [cros_ec_proto]\n cros_ec_cmd_xfer_status+0x1a/0x90 [cros_ec_proto]\n cros_ec_cmd+0xb7/0x140 [cros_ec_proto]\n cros_usbpd_get_event_and_notify+0x42/0xc0 [cros_usbpd_notify]\n acpi_ev_notify_dispatch+0x4e/0x70\n acpi_os_execute_deferred+0x1a/0x30\n\nOnly read the parent\u0027s driver data when the parent\u0027s ACPI node is\nGOOG0004, and otherwise continue without an EC pointer. While at it,\ndrop the reference taken by fwnode_get_parent()."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:12.820Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/4de4a28e514ea2cf9a91d198b66cda7f02ad5edb"
},
{
"url": "https://git.kernel.org/stable/c/ca75b38b1a3c2eabe81d231dae4ea180cf6287cd"
}
],
"title": "platform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99581",
"datePublished": "2026-11-20T05:49:12.820Z",
"dateReserved": "2026-09-25T10:25:14.423Z",
"dateUpdated": "2026-11-20T05:49:12.820Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99581",
"date": "2026-11-20",
"epss": "0.00198",
"percentile": "0.09679"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/platform/chrome/cros_usbpd_notify.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "4de4a28e514ea2cf9a91d198b66cda7f02ad5edb",
"status": "affected",
"version": "e4ee0bb077cd7d70207647a0106f6ea6a74c2636",
"versionType": "git"
},
{
"lessThan": "ca75b38b1a3c2eabe81d231dae4ea180cf6287cd",
"status": "affected",
"version": "e4ee0bb077cd7d70207647a0106f6ea6a74c2636",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/platform/chrome/cros_usbpd_notify.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"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\nplatform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004\n\ncros_usbpd_notify_probe_acpi() takes the EC device pointer from\ndev_get_drvdata(dev-\u003eparent) and assumes it is a struct cros_ec_device.\nThat only holds when GOOG0003 is a child of GOOG0004. On older devices\nwithout that hierarchy, such as Google Nami, GOOG0003 and GOOG0004 are\nsiblings under the ACPI EC (PNP0C09):\n\n PNP0C09:00 (acpi-ec)\n |-- GOOG0003:00 (cros-usbpd-notify-acpi)\n `-- GOOG0004:00 (cros_ec_lpcs)\n\nBefore commit db65a06d10b3 (\"ACPI: EC: Convert the driver to a platform\none\") the parent platform device had no driver data, so the driver\nwarned and continued without an EC pointer, as intended for these\ndevices. Since that commit the ACPI EC driver stores its struct acpi_ec\nthere, so the driver treats a struct acpi_ec as a struct cros_ec_device\nand calls cros_ec_cmd() on it for every USB-C PD host event. Plugging\nor unplugging a charger then intermittently oopses, followed by soft\nlockups and a hung system:\n\n BUG: unable to handle page fault for address: ffffffff9cf03220\n #PF: supervisor write access in kernel mode\n Hardware name: Google Nami/Nami, BIOS 09/19/2019\n Workqueue: kacpi_notify acpi_os_execute_deferred\n RIP: 0010:native_queued_spin_lock_slowpath+0x29d/0x330\n Call Trace:\n _raw_spin_lock_irqsave+0x59/0x80\n __mutex_lock.constprop.0+0x129/0x930\n cros_ec_cmd_xfer+0x2a/0xf0 [cros_ec_proto]\n cros_ec_cmd_xfer_status+0x1a/0x90 [cros_ec_proto]\n cros_ec_cmd+0xb7/0x140 [cros_ec_proto]\n cros_usbpd_get_event_and_notify+0x42/0xc0 [cros_usbpd_notify]\n acpi_ev_notify_dispatch+0x4e/0x70\n acpi_os_execute_deferred+0x1a/0x30\n\nOnly read the parent\u0027s driver data when the parent\u0027s ACPI node is\nGOOG0004, and otherwise continue without an EC pointer. While at it,\ndrop the reference taken by fwnode_get_parent()."
}
],
"id": "CVE-2026-99581",
"lastModified": "2026-11-20T06:17:49.387",
"metrics": {},
"published": "2026-11-20T06:17:49.387",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4de4a28e514ea2cf9a91d198b66cda7f02ad5edb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ca75b38b1a3c2eabe81d231dae4ea180cf6287cd"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T10:20:04+00:00",
"cve": "CVE-2026-99581",
"id": "CVE-2026-99581",
"initial_release_date": "2026-11-20T05:49:12.820000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of service via invalid device data handling in cros_usbpd_notify",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99581.json",
"version": "3"
}
}
}
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.