NVD / CVE Program· CNA Linux

CVE-2023-53003: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 66e10d5f399629ef7877304d9ba2b35d0474e7eb, 6f0351d0c311951b8b3064db91e61841e85b2b96, 76d9ebb7f0bc10fbc78b6d576751552edf743968.

Low priority for now. Upgrade to Linux Linux 66e10d5f399629ef7877304d9ba2b35d0474e7eb, 6f0351d0c311951b8b3064db91e61841e85b2b96, 76d9ebb7f0bc10fbc78b6d576751552edf743968 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info The memory for llcc_driv_data is allocated by the LLCC driver. But when it is passed as the private driver info to the EDAC core, it will get freed during the qcom_edac driver release. So when the qcom_edac driver gets probed again, it will try to use the freed data leading to the use-after-free bug. Hence, do not pass llcc_driv_data as pvt_info but rather reference it using the platform_data pointer in the qcom_edac driver.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-06360

Published: Mar 27, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 18th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel4.20 and later · before 5.4.231
linux linux kernel5.5 and later · before 5.10.166
linux linux kernel5.11 and later · before 5.15.91
linux linux kernel5.16 and later · before 6.1.9
linux linux kernel6.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.20affected
- 27450653f1db0b9d5b5048a246c850c52ee4aa61 and later · before 66e10d5f399629ef7877304d9ba2b35d0474e7ebaffected · git
- 27450653f1db0b9d5b5048a246c850c52ee4aa61 and later · before 76d9ebb7f0bc10fbc78b6d576751552edf743968affected · git
- 27450653f1db0b9d5b5048a246c850c52ee4aa61 and later · before bff5243bd32661cf9ce66f6d9210fc8f89bda145affected · git
- 27450653f1db0b9d5b5048a246c850c52ee4aa61 and later · before 6f0351d0c311951b8b3064db91e61841e85b2b96affected · git
- 27450653f1db0b9d5b5048a246c850c52ee4aa61 and later · before 977c6ba624f24ae20cf0faee871257a39348d4a9affected · git
- before 4.20not affected · semver
- 5.4.231 and later · up to and including 5.4.*not affected · semver
- 5.10.166 and later · up to and including 5.10.*not affected · semver
- 5.15.91 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.11-1	6.1.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2023-53000Mar 27, 2025 · netlink: prevent potential spectre v1 gadgets
31Monitor
← EarlierCVE-2023-53002Mar 27, 2025 · drm/i915: Fix a memory leak with reused mmap_offset
22Monitor
Later →CVE-2023-53004Mar 27, 2025 · ovl: fix tmpfile leak
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	66e10d5f399629ef7877304d9ba2b35d0474e7eb	Vendor (CNA)
Linux Linux	6f0351d0c311951b8b3064db91e61841e85b2b96	Vendor (CNA)
Linux Linux	76d9ebb7f0bc10fbc78b6d576751552edf743968	Vendor (CNA)
Linux Linux	977c6ba624f24ae20cf0faee871257a39348d4a9	Vendor (CNA)
Linux Linux	bff5243bd32661cf9ce66f6d9210fc8f89bda145	Vendor (CNA)
debian:linux	6.1.11-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/66e10d5f399629ef7877304d9ba2b35d0474e7eb

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records