Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52492: dmaengine: fix NULL pointer in channel unregistration function

MediumCVSS 4.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 17/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.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 047fce470412ab64cb7345f9ff5d06919078ad79, 2ab32986a0b9e329eb7f8f04dd57cc127f797c08, 7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50b.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 047fce470412ab64cb7345f9ff5d06919078ad79, 2ab32986a0b9e329eb7f8f04dd57cc127f797c08, 7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50b 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: dmaengine: fix NULL pointer in channel unregistration function __dma_async_device_channel_register() can fail. In case of failure, chan->local is freed (with free_percpu()), and chan->local is nullified. When dma_async_device_unregister() is called (because of managed API or intentionally by DMA controller driver), channels are unconditionally unregistered, leading to this NULL pointer: [ 1.318693] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 [...] [ 1.484499] Call trace: [ 1.486930] device_del+0x40/0x394 [ 1.490314] device_unregister+0x20/0x7c [ 1.494220] __dma_async_device_channel_unregister+0x68/0xc0 Look at dma_async_device_register() function error path, channel device unregistration is done only if chan->local is not NULL. Then add the same condition at the beginning of __dma_async_device_channel_unregister() function, to avoid NULL pointer issue whatever the API used to reach this function.

Published
Mar 11, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.4 / 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-52492

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

  • 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, 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
debiandebian linux

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
    • d2fb0a0438384fee08a418025f743913020033ce and later · before 9de69732dde4e443c1c7f89acbbed2c45a6a8e17affected · git
    • d2fb0a0438384fee08a418025f743913020033ce and later · before 047fce470412ab64cb7345f9ff5d06919078ad79affected · git
    • d2fb0a0438384fee08a418025f743913020033ce and later · before 2ab32986a0b9e329eb7f8f04dd57cc127f797c08affected · git
    • d2fb0a0438384fee08a418025f743913020033ce and later · before 7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50baffected · git
    • d2fb0a0438384fee08a418025f743913020033ce and later · before 9263fd2a63487c6d04cbb7b74a48fb12e1e352d0affected · git
    • d2fb0a0438384fee08a418025f743913020033ce and later · before f5c24d94512f1b288262beda4d3dcb9629222fc7affected · git
    • before 5.6not affected · semver
    • 5.10.210 and later · up to and including 5.10.*not affected · semver
    • 5.15.149 and later · up to and including 5.15.*not affected · semver
Affected versions · NVD (6)

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

  • debian debian linux10.0
  • linux linux kernel5.6 and later · before 5.10.210
  • linux linux kernel5.11 and later · before 5.15.149
  • linux linux kernel5.16 and later · before 6.1.76
  • linux linux kernel6.2 and later · before 6.6.15
  • linux linux kernel6.7 and later · before 6.7.3

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10

+96

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-52489Mar 11, 2024 · mm/sparsemem: fix race in accessing memory_section->usage
    18Monitor
  • ← EarlierCVE-2023-52491Mar 11, 2024 · media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run
    31Monitor
  • Later →CVE-2023-52493Mar 11, 2024 · bus: mhi: host: Drop chan lock before queuing buffers
    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 Linux047fce470412ab64cb7345f9ff5d06919078ad79Vendor (CNA)
Linux Linux2ab32986a0b9e329eb7f8f04dd57cc127f797c08Vendor (CNA)
Linux Linux7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50bVendor (CNA)
Linux Linux9263fd2a63487c6d04cbb7b74a48fb12e1e352d0Vendor (CNA)
Linux Linux9de69732dde4e443c1c7f89acbbed2c45a6a8e17Vendor (CNA)
Linux Linuxf5c24d94512f1b288262beda4d3dcb9629222fc7Vendor (CNA)
almalinux:bpftool4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.216-1~deb10u1 · Debian:10Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.5.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.5.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.5.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:bpftool0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.27.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+10

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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.
  • Administrator privileges are 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
High
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:H/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.

References

Show all references (6 more)

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

All records