Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53275: ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync()

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/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.16% (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 109f0aaa0b8838a88af9125b79579023539300a7, 1f4a08fed450db87fbb5ff5105354158bdbe1a22, 5.4.255.

Low priority for now. Upgrade to Linux Linux 109f0aaa0b8838a88af9125b79579023539300a7, 1f4a08fed450db87fbb5ff5105354158bdbe1a22, 5.4.255 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: ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync() The variable codec->regmap is often protected by the lock codec->regmap_lock when is accessed. However, it is accessed without holding the lock when is accessed in snd_hdac_regmap_sync(): if (codec->regmap) In my opinion, this may be a harmful race, because if codec->regmap is set to NULL right after the condition is checked, a null-pointer dereference can occur in the called function regcache_sync(): map->lock(map->lock_arg); --> Line 360 in drivers/base/regmap/regcache.c To fix this possible null-pointer dereference caused by data race, the mutex_lock coverage is extended to protect the if statement as well as the function call to regcache_sync(). [ Note: the lack of the regmap_lock itself is harmless for the current codec driver implementations, as snd_hdac_regmap_sync() is only for PM runtime resume that is prohibited during the codec probe. But the change makes the whole code more consistent, so it's merged as is -- tiwai ]

Published
Sep 16, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-53275

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 5.6affected
    • 69d5dc286d05441ca2f854ae8df11201f6f9b706 and later · before 109f0aaa0b8838a88af9125b79579023539300a7affected · git
    • 1a462be52f4505a2719631fb5aa7bfdbd37bfd8d and later · before 9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0ebaffected · git
    • 1a462be52f4505a2719631fb5aa7bfdbd37bfd8d and later · before 8703b26387e1fa4f8749db98d24c67617b873acbaffected · git
    • 1a462be52f4505a2719631fb5aa7bfdbd37bfd8d and later · before cdd412b528dee6e0851c4735d6676ec138da13a4affected · git
    • 1a462be52f4505a2719631fb5aa7bfdbd37bfd8d and later · before b32e40379e5b2814de0c4bc199edc2d82317dc07affected · git
    • 1a462be52f4505a2719631fb5aa7bfdbd37bfd8d and later · before 1f4a08fed450db87fbb5ff5105354158bdbe1a22affected · git
    • 5.4.43 and later · before 5.4.255affected · semver
    • before 5.6not affected · semver
    • 5.4.255 and later · up to and including 5.4.*not affected · semver
Affected versions · NVD (5)

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

  • linux linux kernelbefore 5.4.255
  • linux linux kernel5.5 and later · before 5.10.192
  • linux linux kernel5.11 and later · before 5.15.128
  • linux linux kernel5.16 and later · before 6.1.47
  • linux linux kernel6.2 and later · before 6.4.12

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.13-16.4.13-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-53273Sep 16, 2025 · Drivers: vmbus: Check for channel allocation before looking up relids
    22Monitor
  • ← EarlierCVE-2023-53274Sep 16, 2025 · clk: mediatek: mt8183: Add back SSPM related clocks
    31Monitor
  • Later →CVE-2023-53276Sep 16, 2025 · ubifs: Free memory for tmpfile name
    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 / packageFixed versionSource
Linux Linux109f0aaa0b8838a88af9125b79579023539300a7Vendor (CNA)
Linux Linux1f4a08fed450db87fbb5ff5105354158bdbe1a22Vendor (CNA)
Linux Linux5.4.255Vendor (CNA)
Linux Linux8703b26387e1fa4f8749db98d24c67617b873acbVendor (CNA)
Linux Linux9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0ebVendor (CNA)
Linux Linuxb32e40379e5b2814de0c4bc199edc2d82317dc07Vendor (CNA)
Linux Linuxcdd412b528dee6e0851c4735d6676ec138da13a4Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
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:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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.

References

Show all references (5 more)

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

All records