CVE-2026-53300 (GCVE-0-2026-53300)
Vulnerability from cvelistv5 – Published: 2026-06-26 19:40 – Updated: 2026-06-28 06:41
VLAI
Title
net: enetc: fix NTMP DMA use-after-free issue
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: enetc: fix NTMP DMA use-after-free issue
The AI-generated review reported a potential DMA use-after-free issue
[1]. If netc_xmit_ntmp_cmd() times out and returns an error, the pending
command is not explicitly aborted, while ntmp_free_data_mem()
unconditionally frees the DMA buffer. If the buffer has already been
reallocated elsewhere, this may lead to silent memory corruption. Because
the hardware eventually processes the pending command and perform a DMA
write of the response to the physical address of the freed buffer.
To resolve this issue, this patch does the following modifications:
1. Convert cbdr->ring_lock from a spinlock to a mutex
The lock was originally a spinlock in case NTMP operations might be
invoked from atomic context. After downstream support for all NTMP
tables, no such usage has materialized. A mutex lock is now required
because the driver now needs to reclaim used BDs and release associated
DMA memory within the lock's context, while dma_free_coherent() might
sleep.
2. Introduce software command BD (struct netc_swcbd)
The hardware write-back overwrites the addr and len fields of the BD,
so the driver cannot rely on the hardware BD to free the associated DMA
memory. The driver now maintains a software shadow BD storing the DMA
buffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only
reclaims older BDs when the number of used BDs reaches
NETC_CBDR_CLEAN_WORK (16). The software BD enables correct DMA memory
release. With this, struct ntmp_dma_buf and ntmp_free_data_mem() are no
longer needed and are removed.
3. Require callers to hold ring_lock across netc_xmit_ntmp_cmd()
netc_xmit_ntmp_cmd() releases the ring_lock before the caller finishes
consuming the response. At this point, if a concurrent thread submits
a new command, it may trigger ntmp_clean_cbdr() and free the DMA buffer
while it is still in use. Move ring_lock ownership to the caller to
ensure the response buffer cannot be reclaimed prematurely. So the
helpers ntmp_select_and_lock_cbdr() and ntmp_unlock_cbdr() are added.
These changes eliminate the DMA use-after-free condition and ensure safe
and consistent BD reclamation and DMA buffer lifecycle management.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
4701073c3debd16d7f534f3eb808bd9b50601c0c , < 37c8933064be714ee672b0a0523c2fd045b73b3d
(git)
Affected: 4701073c3debd16d7f534f3eb808bd9b50601c0c , < 655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b (git) Affected: 4701073c3debd16d7f534f3eb808bd9b50601c0c , < 3cade698881eb238f88cbbfec82acc2110440a3f (git) |
|
| Linux | Linux |
Affected:
6.16
Unaffected: 0 , < 6.16 (semver) Unaffected: 6.18.33 , ≤ 6.18.* (semver) Unaffected: 7.0.10 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/freescale/enetc/ntmp.c",
"drivers/net/ethernet/freescale/enetc/ntmp_private.h",
"include/linux/fsl/ntmp.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "37c8933064be714ee672b0a0523c2fd045b73b3d",
"status": "affected",
"version": "4701073c3debd16d7f534f3eb808bd9b50601c0c",
"versionType": "git"
},
{
"lessThan": "655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b",
"status": "affected",
"version": "4701073c3debd16d7f534f3eb808bd9b50601c0c",
"versionType": "git"
},
{
"lessThan": "3cade698881eb238f88cbbfec82acc2110440a3f",
"status": "affected",
"version": "4701073c3debd16d7f534f3eb808bd9b50601c0c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/freescale/enetc/ntmp.c",
"drivers/net/ethernet/freescale/enetc/ntmp_private.h",
"include/linux/fsl/ntmp.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"lessThan": "6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.33",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.33",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0.10",
"versionStartIncluding": "6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1",
"versionStartIncluding": "6.16",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: enetc: fix NTMP DMA use-after-free issue\n\nThe AI-generated review reported a potential DMA use-after-free issue\n[1]. If netc_xmit_ntmp_cmd() times out and returns an error, the pending\ncommand is not explicitly aborted, while ntmp_free_data_mem()\nunconditionally frees the DMA buffer. If the buffer has already been\nreallocated elsewhere, this may lead to silent memory corruption. Because\nthe hardware eventually processes the pending command and perform a DMA\nwrite of the response to the physical address of the freed buffer.\n\nTo resolve this issue, this patch does the following modifications:\n\n1. Convert cbdr-\u003ering_lock from a spinlock to a mutex\n\nThe lock was originally a spinlock in case NTMP operations might be\ninvoked from atomic context. After downstream support for all NTMP\ntables, no such usage has materialized. A mutex lock is now required\nbecause the driver now needs to reclaim used BDs and release associated\nDMA memory within the lock\u0027s context, while dma_free_coherent() might\nsleep.\n\n2. Introduce software command BD (struct netc_swcbd)\n\nThe hardware write-back overwrites the addr and len fields of the BD,\nso the driver cannot rely on the hardware BD to free the associated DMA\nmemory. The driver now maintains a software shadow BD storing the DMA\nbuffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only\nreclaims older BDs when the number of used BDs reaches\nNETC_CBDR_CLEAN_WORK (16). The software BD enables correct DMA memory\nrelease. With this, struct ntmp_dma_buf and ntmp_free_data_mem() are no\nlonger needed and are removed.\n\n3. Require callers to hold ring_lock across netc_xmit_ntmp_cmd()\n\nnetc_xmit_ntmp_cmd() releases the ring_lock before the caller finishes\nconsuming the response. At this point, if a concurrent thread submits\na new command, it may trigger ntmp_clean_cbdr() and free the DMA buffer\nwhile it is still in use. Move ring_lock ownership to the caller to\nensure the response buffer cannot be reclaimed prematurely. So the\nhelpers ntmp_select_and_lock_cbdr() and ntmp_unlock_cbdr() are added.\n\nThese changes eliminate the DMA use-after-free condition and ensure safe\nand consistent BD reclamation and DMA buffer lifecycle management."
}
],
"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"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-06-28T06:41:28.036Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/37c8933064be714ee672b0a0523c2fd045b73b3d"
},
{
"url": "https://git.kernel.org/stable/c/655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b"
},
{
"url": "https://git.kernel.org/stable/c/3cade698881eb238f88cbbfec82acc2110440a3f"
}
],
"title": "net: enetc: fix NTMP DMA use-after-free issue",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-53300",
"datePublished": "2026-06-26T19:40:57.186Z",
"dateReserved": "2026-06-09T07:44:35.397Z",
"dateUpdated": "2026-06-28T06:41:28.036Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-53300",
"date": "2026-06-28",
"epss": "0.00124",
"percentile": "0.02471"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-53300\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-06-26T20:17:23.200\",\"lastModified\":\"2026-06-28T08:16:43.273\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: enetc: fix NTMP DMA use-after-free issue\\n\\nThe AI-generated review reported a potential DMA use-after-free issue\\n[1]. If netc_xmit_ntmp_cmd() times out and returns an error, the pending\\ncommand is not explicitly aborted, while ntmp_free_data_mem()\\nunconditionally frees the DMA buffer. If the buffer has already been\\nreallocated elsewhere, this may lead to silent memory corruption. Because\\nthe hardware eventually processes the pending command and perform a DMA\\nwrite of the response to the physical address of the freed buffer.\\n\\nTo resolve this issue, this patch does the following modifications:\\n\\n1. Convert cbdr-\u003ering_lock from a spinlock to a mutex\\n\\nThe lock was originally a spinlock in case NTMP operations might be\\ninvoked from atomic context. After downstream support for all NTMP\\ntables, no such usage has materialized. A mutex lock is now required\\nbecause the driver now needs to reclaim used BDs and release associated\\nDMA memory within the lock\u0027s context, while dma_free_coherent() might\\nsleep.\\n\\n2. Introduce software command BD (struct netc_swcbd)\\n\\nThe hardware write-back overwrites the addr and len fields of the BD,\\nso the driver cannot rely on the hardware BD to free the associated DMA\\nmemory. The driver now maintains a software shadow BD storing the DMA\\nbuffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only\\nreclaims older BDs when the number of used BDs reaches\\nNETC_CBDR_CLEAN_WORK (16). The software BD enables correct DMA memory\\nrelease. With this, struct ntmp_dma_buf and ntmp_free_data_mem() are no\\nlonger needed and are removed.\\n\\n3. Require callers to hold ring_lock across netc_xmit_ntmp_cmd()\\n\\nnetc_xmit_ntmp_cmd() releases the ring_lock before the caller finishes\\nconsuming the response. At this point, if a concurrent thread submits\\na new command, it may trigger ntmp_clean_cbdr() and free the DMA buffer\\nwhile it is still in use. Move ring_lock ownership to the caller to\\nensure the response buffer cannot be reclaimed prematurely. So the\\nhelpers ntmp_select_and_lock_cbdr() and ntmp_unlock_cbdr() are added.\\n\\nThese changes eliminate the DMA use-after-free condition and ensure safe\\nand consistent BD reclamation and DMA buffer lifecycle management.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/net/ethernet/freescale/enetc/ntmp.c\",\"drivers/net/ethernet/freescale/enetc/ntmp_private.h\",\"include/linux/fsl/ntmp.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"4701073c3debd16d7f534f3eb808bd9b50601c0c\",\"lessThan\":\"37c8933064be714ee672b0a0523c2fd045b73b3d\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"4701073c3debd16d7f534f3eb808bd9b50601c0c\",\"lessThan\":\"655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"4701073c3debd16d7f534f3eb808bd9b50601c0c\",\"lessThan\":\"3cade698881eb238f88cbbfec82acc2110440a3f\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/net/ethernet/freescale/enetc/ntmp.c\",\"drivers/net/ethernet/freescale/enetc/ntmp_private.h\",\"include/linux/fsl/ntmp.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.16\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.16\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.33\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0.10\",\"lessThanOrEqual\":\"7.0.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"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\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/37c8933064be714ee672b0a0523c2fd045b73b3d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/3cade698881eb238f88cbbfec82acc2110440a3f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
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…
Loading…