NVD / CVE Program· CNA Linux

CVE-2022-50542: media: si470x: Fix use-after-free in si470x_int_in_callback()

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.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 0ca298d548461d29615f9a2b1309e8dcf4a352c6, 146bd005ebb01ae190c22af050cb98623958c373, 1c6447d0fc68650e51586dde79b5090d9d77f13a.

Low priority for now. Upgrade to Linux Linux 0ca298d548461d29615f9a2b1309e8dcf4a352c6, 146bd005ebb01ae190c22af050cb98623958c373, 1c6447d0fc68650e51586dde79b5090d9d77f13a 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: si470x: Fix use-after-free in si470x_int_in_callback() syzbot reported use-after-free in si470x_int_in_callback() [1]. This indicates that urb->context, which contains struct si470x_device object, is freed when si470x_int_in_callback() is called. The cause of this issue is that si470x_int_in_callback() is called for freed urb. si470x_usb_driver_probe() calls si470x_start_usb(), which then calls usb_submit_urb() and si470x_start(). If si470x_start_usb() fails, si470x_usb_driver_probe() doesn't kill urb, but it just frees struct si470x_device object, as depicted below: si470x_usb_driver_probe() ... si470x_start_usb() ... usb_submit_urb() retval = si470x_start() return retval if (retval < 0) free struct si470x_device object, but don't kill urb This patch fixes this issue by killing urb when si470x_start_usb() fails and urb is submitted. If si470x_start_usb() fails and urb is not submitted, i.e. submitting usb fails, it just frees struct si470x_device object.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-01289

Published: Oct 7, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 5th 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.1%

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 kernel3.6 and later · before 4.9.337
linux linux kernel4.10 and later · before 4.14.303
linux linux kernel4.15 and later · before 4.19.270
linux linux kernel4.20 and later · before 5.4.229
linux linux kernel5.5 and later · before 5.10.163
linux linux kernel5.11 and later · before 5.15.86
linux linux kernel5.16 and later · before 6.0.16
linux linux kernel6.1 and later · before 6.1.2

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
- 3.6affected
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 146bd005ebb01ae190c22af050cb98623958c373affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 8c6151b8e8dd2d98ad2cd725d26d1e103d989891affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 52f54fe78cca24850a30865037250f63eb3d5bf7affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 0ca298d548461d29615f9a2b1309e8dcf4a352c6affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 1c6447d0fc68650e51586dde79b5090d9d77f13aaffected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 63648a7bd1a7599bcc2040a6d1792363ae4c2e1baffected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 92b0888398e4ba51d93b618a6506781f4e3879c9affected · git
- 779471110c6f0f7f7c223fc696170ec750ac3531 and later · before 7d21e0b1b41b21d628bf2afce777727bd4479aa5affected · git

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 6.1.4-1	6.1.4-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-50539Oct 7, 2025 · ARM: OMAP2+: omap4-common: Fix refcount leak bug
22Monitor
← EarlierCVE-2022-50541Oct 7, 2025 · dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow
22Monitor
Later →CVE-2022-50543Oct 7, 2025 · RDMA/rxe: Fix mr->map double free
31Monitor

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	0ca298d548461d29615f9a2b1309e8dcf4a352c6	Vendor (CNA)
Linux Linux	146bd005ebb01ae190c22af050cb98623958c373	Vendor (CNA)
Linux Linux	1c6447d0fc68650e51586dde79b5090d9d77f13a	Vendor (CNA)
Linux Linux	52f54fe78cca24850a30865037250f63eb3d5bf7	Vendor (CNA)
Linux Linux	63648a7bd1a7599bcc2040a6d1792363ae4c2e1b	Vendor (CNA)
Linux Linux	6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75	Vendor (CNA)
Linux Linux	7d21e0b1b41b21d628bf2afce777727bd4479aa5	Vendor (CNA)
Linux Linux	8c6151b8e8dd2d98ad2cd725d26d1e103d989891	Vendor (CNA)
Linux Linux	92b0888398e4ba51d93b618a6506781f4e3879c9	Vendor (CNA)
debian:linux	6.1.4-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-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/0ca298d548461d29615f9a2b1309e8dcf4a352c6

Show all references (8 more)

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

All records