Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52765: mfd: qcom-spmi-pmic: Fix revid implementation

Noroxi assessment

Priority: Monitor (action score 24/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.25% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4ce77b023d42a9f1062eecf438df1af4b4072eb2, 7b439aaa62fee474a0d84d67a25f4984467e7b95, affae18838db5e6b463ee30c821385695af56dc2.

Low priority for now. Upgrade to Linux Linux 4ce77b023d42a9f1062eecf438df1af4b4072eb2, 7b439aaa62fee474a0d84d67a25f4984467e7b95, affae18838db5e6b463ee30c821385695af56dc2 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: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid implementation is broken in multiple ways. First, it assumes that just because the sibling base device has been registered that means that it is also bound to a driver, which may not be the case (e.g. due to probe deferral or asynchronous probe). This could trigger a NULL-pointer dereference when attempting to access the driver data of the unbound device. Second, it accesses driver data of a sibling device directly and without any locking, which means that the driver data may be freed while it is being accessed (e.g. on driver unbind). Third, it leaks a struct device reference to the sibling device which is looked up using the spmi_device_from_of() every time a function (child) device is calling the revid function (e.g. on probe). Fix this mess by reimplementing the revid lookup so that it is done only at probe of the PMIC device; the base device fetches the revid info from the hardware, while any secondary SPMI device fetches the information from the base device and caches it so that it can be accessed safely from its children. If the base device has not been probed yet then probe of a secondary device is deferred.

MediumCVSS 6.2 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

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.

Follow CVE-2023-52765

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel6.0 and later · before 6.1.64
  • linux linux kernel6.2 and later · before 6.5.13
  • linux linux kernel6.6 and later · before 6.6.3

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

    • 6.0affected
    • e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 and later · before db98de0809f12b0edb9cd1be78e1ec1bfeba8f40affected · git
    • e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 and later · before 4ce77b023d42a9f1062eecf438df1af4b4072eb2affected · git
    • e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 and later · before affae18838db5e6b463ee30c821385695af56dc2affected · git
    • e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 and later · before 7b439aaa62fee474a0d84d67a25f4984467e7b95affected · git
    • before 6.0not affected · semver
    • 6.1.64 and later · up to and including 6.1.*not affected · semver
    • 6.5.13 and later · up to and including 6.5.*not affected · semver
    • 6.6.3 and later · up to and including 6.6.*not affected · semver
    • 6.7 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.64-16.1.64-1
Debian:13linuxbefore 6.6.8-16.6.8-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.14.16.4.0-150600.23.14.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.14.16.4.0-150600.23.14.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.14.2.150600.12.4.36.4.0-150600.23.14.2.150600.12.4.3
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_2before 1-150600.13.3.21-150600.13.3.2
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-64kbbefore 6.4.0-150600.23.14.16.4.0-150600.23.14.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-defaultbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-default-basebefore 6.4.0-150600.23.14.2.150600.12.4.36.4.0-150600.23.14.2.150600.12.4.3
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-sourcebefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-zfcpdumpbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Module for Development Tools 15 SP6kernel-docsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Module for Development Tools 15 SP6kernel-obs-buildbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2
SUSE:Linux Enterprise Module for Development Tools 15 SP6kernel-symsbefore 6.4.0-150600.23.14.26.4.0-150600.23.14.2

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-52763May 21, 2024 · i3c: master: mipi-i3c-hci: Fix a kernel panic for accessing DAT_data.
    22Monitor
  • ← EarlierCVE-2023-52764May 21, 2024 · media: gspca: cpia1: shift-out-of-bounds in set_flicker
    31Monitor
  • Later →CVE-2023-52766May 21, 2024 · i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler
    28Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux4ce77b023d42a9f1062eecf438df1af4b4072eb2Vendor (CNA)
Linux Linux7b439aaa62fee474a0d84d67a25f4984467e7b95Vendor (CNA)
Linux Linuxaffae18838db5e6b463ee30c821385695af56dc2Vendor (CNA)
Linux Linuxdb98de0809f12b0edb9cd1be78e1ec1bfeba8f40Vendor (CNA)
debian:linux6.1.64-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.14.2.150600.12.4.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-zfcpdump6.4.0-150600.23.14.2 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.14.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.14.2.150600.12.4.3 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-docs6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_21-150600.13.3.2 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-syms6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-zfcpdump6.4.0-150600.23.14.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package 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.

No history yet (it accumulates with the daily EPSS job).

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.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

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

nvd-secondary

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

  1. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records