CVE-2023-54083 (GCVE-0-2023-54083)
Vulnerability from cvelistv5 – Published: 2025-12-24 13:06 – Updated: 2026-08-05 09:17
VLAI
EPSS
VEX
Title
phy: tegra: xusb: Clear the driver reference in usb-phy dev
Summary
In the Linux kernel, the following vulnerability has been resolved:
phy: tegra: xusb: Clear the driver reference in usb-phy dev
For the dual-role port, it will assign the phy dev to usb-phy dev and
use the port dev driver as the dev driver of usb-phy.
When we try to destroy the port dev, it will destroy its dev driver
as well. But we did not remove the reference from usb-phy dev. This
might cause the use-after-free issue in KASAN.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
e8f7d2f409a15c519d5a6085777d85c1c4bab73a , < b6a107c52073496d2e5d2837915f59fb3103832f
(git)
Affected: e8f7d2f409a15c519d5a6085777d85c1c4bab73a , < b84998a407a882991916b1a61d987c400d8a0ce6 (git) Affected: e8f7d2f409a15c519d5a6085777d85c1c4bab73a , < 238edc04ddb9d272b38f5419bcd419ad3b92b91b (git) Affected: e8f7d2f409a15c519d5a6085777d85c1c4bab73a , < 82187460347ad58fd6b06d2883da73c3f2df9631 (git) Affected: e8f7d2f409a15c519d5a6085777d85c1c4bab73a , < c0c2fcb1325d0d4f3b322b5ee49385f8eca2560d (git) |
guessed | |
| Linux | Linux |
Affected:
5.7
Unaffected: 0 , < 5.7 (semver) Unaffected: 5.10.188 , ≤ 5.10.* (semver) Unaffected: 5.15.121 , ≤ 5.15.* (semver) Unaffected: 6.1.39 , ≤ 6.1.* (semver) Unaffected: 6.4.4 , ≤ 6.4.* (semver) Unaffected: 6.5 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/phy/tegra/xusb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "b6a107c52073496d2e5d2837915f59fb3103832f",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "b84998a407a882991916b1a61d987c400d8a0ce6",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "238edc04ddb9d272b38f5419bcd419ad3b92b91b",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "82187460347ad58fd6b06d2883da73c3f2df9631",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "c0c2fcb1325d0d4f3b322b5ee49385f8eca2560d",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/phy/tegra/xusb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.7"
},
{
"lessThan": "5.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.121",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.39",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.4.*",
"status": "unaffected",
"version": "6.4.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.5",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.188",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.121",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.39",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.4.4",
"versionStartIncluding": "5.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.5",
"versionStartIncluding": "5.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nphy: tegra: xusb: Clear the driver reference in usb-phy dev\n\nFor the dual-role port, it will assign the phy dev to usb-phy dev and\nuse the port dev driver as the dev driver of usb-phy.\n\nWhen we try to destroy the port dev, it will destroy its dev driver\nas well. But we did not remove the reference from usb-phy dev. This\nmight cause the use-after-free issue in KASAN."
}
],
"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 - The vulnerability is reached through the tegra-xusb-padctl platform driver teardown/probe-failure path, which is driven from local system interfaces (sysfs unbind, module unload) and local process activity, not from any network or peer-supplied data. No physical device insertion is needed since the padctl is an on-SoC platform device.\nAC:L - The dangling `dev.driver` and its subsequent dereference occur deterministically in the same teardown sequence \u2014 `devres_release_all()` frees the fake `device_driver` in `device_del(\u0026port-\u003edev)` and `phy_destroy()` reads it moments later \u2014 with no race the attacker cannot influence. The freed object is a small kmalloc allocation that a local attacker can reliably groom.\nPR:L - Exploitation of the freed `struct device_driver` \u2014 spraying the slab so the driver core reads attacker-controlled `pm`/`name` fields \u2014 is performed by an ordinary unprivileged local process, and the same teardown also executes on the boot-time probe-failure path with no privilege at all. Consistent with prior scoring of driver-remove-path use-after-frees in this subsystem class, PR:L is the higher defensible value.\nUI:N - No victim action is required; the use-after-free occurs automatically within the driver removal/probe-failure sequence. The attacker only needs to have its heap spray in place.\nS:U - Both the freed object and the code dereferencing it live in the kernel\u0027s own security authority, with no crossing of a VM, IOMMU, or sandbox boundary. This is a standard in-kernel memory-safety defect.\nC:H - The stale pointer is read by `dev_driver_string()` (`drv-\u003ename` passed to printk) and by `device_pm_check_callbacks()`, so reallocated heap contents can be dereferenced and leaked into kernel logs. Per use-after-free guidance, control over the freed object\u0027s contents yields an arbitrary-read primitive.\nI:H - `__rpm_get_callback()` loads a function pointer out of `dev-\u003edriver-\u003epm` on the freed object and invokes it, giving a direct control-flow hijack primitive once the slab object is reallocated with attacker-controlled data. Use-after-free of a structure containing function pointers is treated as High integrity impact.\nA:H - The KASAN-reported use-after-free dereferences freed memory during device removal, producing an oops or panic even without deliberate exploitation. Any kernel crash is scored High."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T09:17:04.479Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/b6a107c52073496d2e5d2837915f59fb3103832f"
},
{
"url": "https://git.kernel.org/stable/c/b84998a407a882991916b1a61d987c400d8a0ce6"
},
{
"url": "https://git.kernel.org/stable/c/238edc04ddb9d272b38f5419bcd419ad3b92b91b"
},
{
"url": "https://git.kernel.org/stable/c/82187460347ad58fd6b06d2883da73c3f2df9631"
},
{
"url": "https://git.kernel.org/stable/c/c0c2fcb1325d0d4f3b322b5ee49385f8eca2560d"
}
],
"title": "phy: tegra: xusb: Clear the driver reference in usb-phy dev",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2023-54083",
"datePublished": "2025-12-24T13:06:14.771Z",
"dateReserved": "2025-12-24T13:02:52.515Z",
"dateUpdated": "2026-08-05T09:17:04.479Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2023-54083",
"date": "2026-09-19",
"epss": "0.00159",
"percentile": "0.05539"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/phy/tegra/xusb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "b6a107c52073496d2e5d2837915f59fb3103832f",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "b84998a407a882991916b1a61d987c400d8a0ce6",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "238edc04ddb9d272b38f5419bcd419ad3b92b91b",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "82187460347ad58fd6b06d2883da73c3f2df9631",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
},
{
"lessThan": "c0c2fcb1325d0d4f3b322b5ee49385f8eca2560d",
"status": "affected",
"version": "e8f7d2f409a15c519d5a6085777d85c1c4bab73a",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/phy/tegra/xusb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.7"
},
{
"lessThan": "5.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.121",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.39",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.4.*",
"status": "unaffected",
"version": "6.4.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.5",
"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\nphy: tegra: xusb: Clear the driver reference in usb-phy dev\n\nFor the dual-role port, it will assign the phy dev to usb-phy dev and\nuse the port dev driver as the dev driver of usb-phy.\n\nWhen we try to destroy the port dev, it will destroy its dev driver\nas well. But we did not remove the reference from usb-phy dev. This\nmight cause the use-after-free issue in KASAN."
}
],
"id": "CVE-2023-54083",
"lastModified": "2026-08-04T10:19:28.120",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2025-12-24T13:16:10.147",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/238edc04ddb9d272b38f5419bcd419ad3b92b91b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/82187460347ad58fd6b06d2883da73c3f2df9631"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b6a107c52073496d2e5d2837915f59fb3103832f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b84998a407a882991916b1a61d987c400d8a0ce6"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c0c2fcb1325d0d4f3b322b5ee49385f8eca2560d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Deferred"
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-08-04T22:52:27+00:00",
"cve": "CVE-2023-54083",
"id": "CVE-2023-54083",
"initial_release_date": "2023-01-01T00:00:00+00:00",
"product_status:fixed": "280",
"product_status:known_affected": "22",
"product_status:known_not_affected": "174",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: phy: tegra: xusb: Clear the driver reference in usb-phy dev",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-54083.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-08-29T02:04:01Z",
"cve": "CVE-2023-54083",
"id": "CVE-2023-54083",
"initial_release_date": "2025-12-25T00:56:02Z",
"product_status:known_affected": "401",
"product_status:known_not_affected": "236",
"product_status:recommended": "408",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2023-54083",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2023-54083.json",
"version": "35"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…