NVD / CVE Program· CNA Linux

CVE-2023-52491: media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run

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.27% (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 1b1036c60a37a30caf6759a90fe5ecd06ec35590, 206c857dd17d4d026de85866f1b5f0969f2a109e, 43872f44eee6c6781fea1348b38885d8e78face9.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1b1036c60a37a30caf6759a90fe5ecd06ec35590, 206c857dd17d4d026de85866f1b5f0969f2a109e, 43872f44eee6c6781fea1348b38885d8e78face9 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: media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run In mtk_jpeg_probe, &jpeg->job_timeout_work is bound with mtk_jpeg_job_timeout_work. In mtk_jpeg_dec_device_run, if error happens in mtk_jpeg_set_dec_dst, it will finally start the worker while mark the job as finished by invoking v4l2_m2m_job_finish. There are two methods to trigger the bug. If we remove the module, it which will call mtk_jpeg_remove to make cleanup. The possible sequence is as follows, which will cause a use-after-free bug. CPU0 CPU1 mtk_jpeg_dec_... | start worker | |mtk_jpeg_job_timeout_work mtk_jpeg_remove | v4l2_m2m_release | kfree(m2m_dev); | | | v4l2_m2m_get_curr_priv | m2m_dev->curr_ctx //use If we close the file descriptor, which will call mtk_jpeg_release, it will have a similar sequence. Fix this bug by starting timeout worker only if started jpegdec worker successfully. Then v4l2_m2m_job_finish will only be called in either mtk_jpeg_job_timeout_work or mtk_jpeg_dec_device_run.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Mar 11, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 20th 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: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.12 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

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.12affected
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 43872f44eee6c6781fea1348b38885d8e78face9affected · git
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 1b1036c60a37a30caf6759a90fe5ecd06ec35590affected · git
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 9fec4db7fff54d9b0306a332bab31eac47eeb5f6affected · git
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 8254d54d00eb6cdb8367399c7f912eb8d354ecd7affected · git
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 6e2f37022f0fc0893da4d85a0500c9d547fffd4caffected · git
- b2f0d2724ba477d326e9d654d4db1c93e98f8b93 and later · before 206c857dd17d4d026de85866f1b5f0969f2a109eaffected · git
- before 4.12not 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

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:10	linux-5.10	before 5.10.216-1~deb10u1	5.10.216-1~deb10u1
Debian:11	linux	before 5.10.216-1	5.10.216-1
Debian:12	linux	before 6.1.76-1	6.1.76-1
Debian:13	linux	before 6.6.15-1	6.6.15-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-52488Mar 11, 2024 · serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO
22Monitor
← EarlierCVE-2023-52489Mar 11, 2024 · mm/sparsemem: fix race in accessing memory_section->usage
18Monitor
Later →CVE-2023-52492Mar 11, 2024 · dmaengine: fix NULL pointer in channel unregistration function
17Monitor

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	1b1036c60a37a30caf6759a90fe5ecd06ec35590	Vendor (CNA)
Linux Linux	206c857dd17d4d026de85866f1b5f0969f2a109e	Vendor (CNA)
Linux Linux	43872f44eee6c6781fea1348b38885d8e78face9	Vendor (CNA)
Linux Linux	6e2f37022f0fc0893da4d85a0500c9d547fffd4c	Vendor (CNA)
Linux Linux	8254d54d00eb6cdb8367399c7f912eb8d354ecd7	Vendor (CNA)
Linux Linux	9fec4db7fff54d9b0306a332bab31eac47eeb5f6	Vendor (CNA)
debian:linux	6.1.76-1 · Debian:12	Package registry (OSV)
debian:linux-5.10	5.10.216-1~deb10u1 · Debian:10	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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

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

TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)

All national notices →

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

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:11 PM UTC

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

References

git.kernel.org/stable/c/1b1036c60a37a30caf6759a90fe5ecd06ec35590

Show all references (6 more)

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

All records