{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-72485", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-08-09T03:40:39.935Z", "datePublished": "2026-08-15T05:57:22.170Z", "dateUpdated": "2026-08-17T05:44:47.818Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-17T05:44:47.818Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: platform: defer connection counter increment until alloc succeeds\n\ncoresight_add_out_conn() increments nr_outconns before calling\ndevm_krealloc_array() and again before devm_kmalloc(). If either\nallocation fails, the counter is already bumped while the corresponding\narray entry is NULL or uninitialized garbage.\n\ncoresight_add_in_conn() has the same problem with nr_inconns and\ndevm_krealloc_array().\n\nIn both cases the probe returns -ENOMEM, which causes\ncoresight_get_platform_data() to call coresight_release_platform_data()\nfor cleanup. That function iterates up to nr_outconns (or nr_inconns)\nentries and dereferences each pointer unconditionally, hitting the NULL\nor garbage entry and panicking instead of failing gracefully.\n\nFix by moving the counter increments to after all allocations succeed,\nso the struct is always consistent on any error path."}], "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 flaw is in ARM CoreSight platform driver probe (coresight_get_platform_data/coresight_add_out_conn) while parsing firmware DT/ACPI connection graphs during local device initialization; there is no network, Bluetooth, or physical-bus path to this code.\nAC:L - An attacker can reliably force devm_kmalloc/devm_krealloc failure via memory exhaustion and time it with deferred CoreSight probe retries; success does not depend on uncontrollable layout or victim state beyond attacker-driven memory pressure.\nPR:L - Only a local unprivileged process is needed to exhaust memory; CoreSight drivers commonly reprobe after -EPROBE_DEFER once dependencies appear, so no init-namespace root, CAP_SYS_MODULE, or CAP_NET_ADMIN is required to reach the failing cleanup path.\nUI:N - No victim interaction is required; the attacker alone can create memory pressure and rely on automatic deferred driver reprobe without anyone mounting devices, opening files, or clicking prompts.\nS:U - Impact is a kernel panic and in-kernel memory corruption within the same kernel security authority; CoreSight is an on-chip trace/debug subsystem and this is not a VM escape, IOMMU bypass, or sandbox boundary crossing.\nC:H - If krealloc succeeds but the connection kmalloc fails, nr_outconns is already inflated while out_conns contains an uninitialized garbage pointer; coresight_release_platform_data() unconditionally dereferences conns[i]->dest_fwnode, enabling arbitrary kernel memory reads before panic.\nI:H - Error cleanup calls fwnode_handle_put() and devm_kfree() on NULL or garbage connection pointers, corrupting kernel refcount/heap metadata and creating exploitable write primitives beyond a benign NULL dereference crash.\nA:H - The inconsistent nr_outconns counter makes coresight_release_platform_data() dereference NULL or garbage entries during probe error cleanup, causing a kernel oops/panic and total system unavailability on affected ARM/ARM64 platforms (phones, embedded, automotive, cloud)."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/hwtracing/coresight/coresight-platform.c"], "versions": [{"version": "3d4ff657e454f8dba3e5e268e731e6e28c6031c1", "lessThan": "8ca9adc805884d3bb5038082462577f86c2c4a10", "status": "affected", "versionType": "git"}, {"version": "3d4ff657e454f8dba3e5e268e731e6e28c6031c1", "lessThan": "1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae", "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/hwtracing/coresight/coresight-platform.c"], "versions": [{"version": "6.5", "status": "affected"}, {"version": "0", "lessThan": "6.5", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.5", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "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": "6.5", "versionEndExcluding": "7.1.5"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.5", "versionEndExcluding": "7.2"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/8ca9adc805884d3bb5038082462577f86c2c4a10"}, {"url": "https://git.kernel.org/stable/c/1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae"}], "title": "coresight: platform: defer connection counter increment until alloc succeeds", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["drivers/hwtracing/coresight/coresight-platform.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "8ca9adc805884d3bb5038082462577f86c2c4a10", "status": "affected", "version": "3d4ff657e454f8dba3e5e268e731e6e28c6031c1", "versionType": "git"}, {"lessThan": "1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae", "status": "affected", "version": "3d4ff657e454f8dba3e5e268e731e6e28c6031c1", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["drivers/hwtracing/coresight/coresight-platform.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.5"}, {"lessThan": "6.5", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "7.1.*", "status": "unaffected", "version": "7.1.5", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.2", "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\ncoresight: platform: defer connection counter increment until alloc succeeds\n\ncoresight_add_out_conn() increments nr_outconns before calling\ndevm_krealloc_array() and again before devm_kmalloc(). If either\nallocation fails, the counter is already bumped while the corresponding\narray entry is NULL or uninitialized garbage.\n\ncoresight_add_in_conn() has the same problem with nr_inconns and\ndevm_krealloc_array().\n\nIn both cases the probe returns -ENOMEM, which causes\ncoresight_get_platform_data() to call coresight_release_platform_data()\nfor cleanup. That function iterates up to nr_outconns (or nr_inconns)\nentries and dereferences each pointer unconditionally, hitting the NULL\nor garbage entry and panicking instead of failing gracefully.\n\nFix by moving the counter increments to after all allocations succeed,\nso the struct is always consistent on any error path."}], "id": "CVE-2026-72485", "lastModified": "2026-08-17T06:19:16.710", "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": "2026-08-15T06:22:22.767", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/8ca9adc805884d3bb5038082462577f86c2c4a10"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: coresight: platform: defer connection counter increment until alloc succeeds", "id": "2516614", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2516614"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-476", "details": ["In the Linux kernel, the following vulnerability has been resolved:\ncoresight: platform: defer connection counter increment until alloc succeeds\ncoresight_add_out_conn() increments nr_outconns before calling\ndevm_krealloc_array() and again before devm_kmalloc(). If either\nallocation fails, the counter is already bumped while the corresponding\narray entry is NULL or uninitialized garbage.\ncoresight_add_in_conn() has the same problem with nr_inconns and\ndevm_krealloc_array().\nIn both cases the probe returns -ENOMEM, which causes\ncoresight_get_platform_data() to call coresight_release_platform_data()\nfor cleanup. That function iterates up to nr_outconns (or nr_inconns)\nentries and dereferences each pointer unconditionally, hitting the NULL\nor garbage entry and panicking instead of failing gracefully.\nFix by moving the counter increments to after all allocations succeed,\nso the struct is always consistent on any error path.", "A flaw was found in the Linux kernel's coresight platform component. The functions responsible for adding input and output connections increment internal counters before successfully allocating memory. If a memory allocation fails, these counters become inconsistent with the actual state of allocated resources. This inconsistency can lead to the system attempting to access uninitialized or invalid memory during error cleanup, causing a system panic and resulting in a Denial of Service (DoS)."], "name": "CVE-2026-72485", "public_date": "2026-08-15T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-72485\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-72485\nhttps://lore.kernel.org/linux-cve-announce/2026081537-CVE-2026-72485-81e7@gregkh/T"], "threat_severity": "Low"}