NVD / CVE Program· CNA Linux

CVE-2022-49493: ASoC: rt5645: Fix errorenous cleanup order

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 061a6159cea583f1155f67d1915917a6b9282662, 0941150100173d4eaf3fe08ff4b16740e7c3026f, 1a5a3dfd9f172dcb115072f0aea5e27d3083c20e.

Low priority for now. Upgrade to Linux Linux 061a6159cea583f1155f67d1915917a6b9282662, 0941150100173d4eaf3fe08ff4b16740e7c3026f, 1a5a3dfd9f172dcb115072f0aea5e27d3083c20e 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: ASoC: rt5645: Fix errorenous cleanup order There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and delete the &rt5645->btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy. That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free. This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-04425

Published: Feb 26, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 19th 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.

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 kernelbefore 4.9.318
linux linux kernel4.10 and later · before 4.14.283
linux linux kernel4.15 and later · before 4.19.247
linux linux kernel4.20 and later · before 5.4.198
linux linux kernel5.5 and later · before 5.10.121
linux linux kernel5.11 and later · before 5.15.46
linux linux kernel5.16 and later · before 5.17.14
linux linux kernel5.18 and later · before 5.18.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.13affected
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 236d29c5857f02e0a53fdf15d3dce1536c4322ceaffected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 0941150100173d4eaf3fe08ff4b16740e7c3026faffected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before abe7554da62cb489712a54de69ef5665c250e564affected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 1a5a3dfd9f172dcb115072f0aea5e27d3083c20eaffected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 061a6159cea583f1155f67d1915917a6b9282662affected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 88c09e4812d72c3153afc8e5a45ecac2d0eae3ffaffected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 453f0920ffc1a28e28ddb9c3cd5562472b2895b0affected · git
- a6ff8ddcf3f38ec84337e5e7eb3e0e9a73754cf5 and later · before 2def44d3aec59e38d2701c568d65540783f90f2faffected · git
- before 4.13not 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 5.18.5-1	5.18.5-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-2022-49491Feb 26, 2025 · drm/rockchip: vop: fix possible null-ptr-deref in vop_bind()
22Monitor
← EarlierCVE-2022-49492Feb 26, 2025 · nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags
22Monitor
Later →CVE-2022-49494Feb 26, 2025 · mtd: rawnand: cadence: fix possible null-ptr-deref in cadence_nand_dt_probe()
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	061a6159cea583f1155f67d1915917a6b9282662	Vendor (CNA)
Linux Linux	0941150100173d4eaf3fe08ff4b16740e7c3026f	Vendor (CNA)
Linux Linux	1a5a3dfd9f172dcb115072f0aea5e27d3083c20e	Vendor (CNA)
Linux Linux	236d29c5857f02e0a53fdf15d3dce1536c4322ce	Vendor (CNA)
Linux Linux	2def44d3aec59e38d2701c568d65540783f90f2f	Vendor (CNA)
Linux Linux	453f0920ffc1a28e28ddb9c3cd5562472b2895b0	Vendor (CNA)
Linux Linux	88c09e4812d72c3153afc8e5a45ecac2d0eae3ff	Vendor (CNA)
Linux Linux	abe7554da62cb489712a54de69ef5665c250e564	Vendor (CNA)
debian:linux	5.18.5-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.

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.
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:10 PM UTC

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

References

git.kernel.org/stable/c/061a6159cea583f1155f67d1915917a6b9282662

Show all references (7 more)

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

All records