159 lines
10 KiB
JSON
159 lines
10 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2023-54065",
|
|
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "Linux",
|
|
"dateReserved": "2025-12-24T12:21:05.092Z",
|
|
"datePublished": "2025-12-24T12:23:10.745Z",
|
|
"dateUpdated": "2026-08-05T09:16:53.228Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"shortName": "Linux",
|
|
"dateUpdated": "2026-08-05T09:16:53.228Z"
|
|
},
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: realtek: fix out-of-bounds access\n\nThe probe function sets priv->chip_data to (void *)priv + sizeof(*priv)\nwith the expectation that priv has enough trailing space.\n\nHowever, only realtek-smi actually allocated this chip_data space.\nDo likewise in realtek-mdio to fix out-of-bounds accesses.\n\nThese accesses likely went unnoticed so far, because of an (unused)\nbuf[4096] member in struct realtek_priv, which caused kmalloc to\nround up the allocated buffer to a big enough size, so nothing of\nvalue was overwritten. With a different allocator (like in the barebox\nbootloader port of the driver) or with KASAN, the memory corruption\nbecomes quickly apparent."
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
|
"baseScore": 7.8,
|
|
"baseSeverity": "HIGH"
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "AV:L - The defect is in a DSA switch driver probe path bound via device tree, and the reachable trigger surfaces are local — driver probe at boot, `ip -s link`/sysfs stat reads, and `ip link set mtu`/VLAN configuration on the DSA slave ports. No received network frame or remote peer data reaches the miscalculated `chip_data` pointer, so neither Network nor Adjacent applies.\nAC:L - The miscalculation is unconditional: every single probe of `realtek-mdio` sets `chip_data` past the end of the allocation, and every subsequent access is out of bounds with no race, timing window, or memory-layout precondition. Reading the leaked stale heap back out requires only an unprivileged `ip -s link`, and the affected chips (RTL8366RB, RTL8365MB-VC, RTL8367S) are mainstream in shipped router/embedded kernels, not a rare configuration.\nPR:L - The out-of-bounds writes occur automatically during boot-time probe with no attacker involvement at all, and the resulting kernel-heap disclosure is harvested through `ndo_get_stats64` counters that any unprivileged local process can read from `/sys/class/net/*/statistics/*` with no `capable()` check anywhere on the path. Only the additional MTU/VLAN write primitives need `CAP_NET_ADMIN`, so a basic unprivileged user is the correct floor.\nUI:N - No victim action is required — the corruption is established by the driver itself at probe and the periodic `mib_work` poller keeps touching the out-of-bounds region on its own. The attacker's own process reads the leaked bytes back with no interaction from any other user.\nS:U - The miscalculated pointer, the corrupted slab memory, and the impacted component are all the same kernel image and the same security authority. There is no guest-to-host escape, IOMMU bypass, or sandbox boundary crossed.\nC:H - `rtl8365mb_get_stats64()` memcpy's 192 bytes per port (11 ports) out of the never-zeroed tail of the slab object — stale data recycled from a previously freed allocation — directly into netdev statistics that any unprivileged user can read, an unbounded-content kernel heap disclosure that works on every configuration. All the other `chip_data` reads (`mb->chip_info`, `rb->max_mtu[]`, `rb->pvid_enabled[]`) are likewise out-of-bounds reads of adjacent memory.\nI:H - This is an out-of-bounds write, which is High by definition: probe writes an entire `struct rtl8365mb` — including `mutex`, `spinlock_t`, and eleven `delayed_work`/`timer_list` structures carrying kernel function pointers — past the end of the allocation, and `rtl8366rb_change_mtu()` writes an attacker-supplied MTU value there at runtime. Because that OOB-resident work item's function pointer is repeatedly armed and dereferenced by `schedule_delayed_work()`, corruption of an overlapping slab object yields a control-flow-relevant primitive rather than a mere data clobber.\nA:H - Under KASAN the access produces an immediate slab-out-of-bounds report (panic with `panic_on_warn`), and under SLUB redzoning the overwritten poison triggers a corruption BUG at free. On lockdep/debug-instrumented builds the inflated lock and work structures push the required size past the `kmalloc-8192` bucket so the write lands in a neighbouring live object, and a timer whose function pointer resides in that clobbered memory is dereferenced periodically — a reliable route to an oops or panic."
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"affected": [
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "unaffected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"drivers/net/dsa/realtek/realtek-mdio.c"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "aac94001067da183455d6d37959892744fa01d9d",
|
|
"lessThan": "cc0f9bb99735d2b68fac68f37b585d615728ce5b",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
},
|
|
{
|
|
"version": "aac94001067da183455d6d37959892744fa01d9d",
|
|
"lessThan": "fe668aa499b4b95425044ba11af9609db6ecf466",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
},
|
|
{
|
|
"version": "aac94001067da183455d6d37959892744fa01d9d",
|
|
"lessThan": "b93eb564869321d0dffaf23fcc5c88112ed62466",
|
|
"status": "affected",
|
|
"versionType": "git"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"product": "Linux",
|
|
"vendor": "Linux",
|
|
"defaultStatus": "affected",
|
|
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
|
|
"programFiles": [
|
|
"drivers/net/dsa/realtek/realtek-mdio.c"
|
|
],
|
|
"versions": [
|
|
{
|
|
"version": "5.18",
|
|
"status": "affected"
|
|
},
|
|
{
|
|
"version": "0",
|
|
"lessThan": "5.18",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.1.23",
|
|
"lessThanOrEqual": "6.1.*",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.2.10",
|
|
"lessThanOrEqual": "6.2.*",
|
|
"status": "unaffected",
|
|
"versionType": "semver"
|
|
},
|
|
{
|
|
"version": "6.3",
|
|
"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": "5.18",
|
|
"versionEndExcluding": "6.1.23"
|
|
},
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "5.18",
|
|
"versionEndExcluding": "6.2.10"
|
|
},
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "5.18",
|
|
"versionEndExcluding": "6.3"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/cc0f9bb99735d2b68fac68f37b585d615728ce5b"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/fe668aa499b4b95425044ba11af9609db6ecf466"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/b93eb564869321d0dffaf23fcc5c88112ed62466"
|
|
}
|
|
],
|
|
"title": "net: dsa: realtek: fix out-of-bounds access",
|
|
"x_generator": {
|
|
"engine": "bippy-1.2.0"
|
|
}
|
|
}
|
|
}
|
|
} |