{"api_version":"1","generated_at":"2026-08-31T20:53:19+00:00","cve":"CVE-2026-72485","urls":{"html":"https://cve.report/CVE-2026-72485","api":"https://cve.report/api/cve/CVE-2026-72485.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72485","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72485"},"summary":{"title":"coresight: platform: defer connection counter increment until alloc succeeds","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:22","updated_at":"2026-08-17 06:19:16"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"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"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"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"}}],"references":[{"url":"https://git.kernel.org/stable/c/8ca9adc805884d3bb5038082462577f86c2c4a10","name":"https://git.kernel.org/stable/c/8ca9adc805884d3bb5038082462577f86c2c4a10","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae","name":"https://git.kernel.org/stable/c/1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72485","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72485","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 8ca9adc805884d3bb5038082462577f86c2c4a10 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.5","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72485","cve":"CVE-2026-72485","epss":"0.001540000","percentile":"0.050630000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:46"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"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"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.5","vulnerable":true}],"negate":false,"operator":"OR"}]}],"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":{"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 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)."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:44:47.818Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"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"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-72485","datePublished":"2026-08-15T05:57:22.170Z","dateReserved":"2026-08-09T03:40:39.935Z","dateUpdated":"2026-08-17T05:44:47.818Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:22","lastModifiedDate":"2026-08-17 06:19:16","problem_types":[],"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}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72485","Ordinal":"1","Title":"coresight: platform: defer connection counter increment until al","CVE":"CVE-2026-72485","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72485","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"coresight: platform: defer connection counter increment until al"}]}}}