NVD / CVE Program· CNA Linux

CVE-2022-50240: android: binder: stop saving a pointer to the VMA

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 015ac18be7de25d17d6e5f1643cb3b60bfbe859e, 1ec3f76a436d750fd5023caec5da0494fc2870d2, 27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b.

Low priority for now. Upgrade to Linux Linux 015ac18be7de25d17d6e5f1643cb3b60bfbe859e, 1ec3f76a436d750fd5023caec5da0494fc2870d2, 27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b 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: android: binder: stop saving a pointer to the VMA Do not record a pointer to a VMA outside of the mmap_lock for later use. This is unsafe and there are a number of failure paths *after* the recorded VMA pointer may be freed during setup. There is no callback to the driver to clear the saved pointer from generic mm code. Furthermore, the VMA pointer may become stale if any number of VMA operations end up freeing the VMA so saving it was fragile to being with. Instead, change the binder_alloc struct to record the start address of the VMA and use vma_lookup() to get the vma when needed. Add lockdep mmap_lock checks on updates to the vma pointer to ensure the lock is held and depend on that lock for synchronization of readers and writers - which was already the case anyways, so the smp_wmb()/smp_rmb() was not necessary. [akpm@linux-foundation.org: fix drivers/android/binder_alloc_selftest.c]

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-08827

Published: Sep 15, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 6th 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%

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.20 and later · before 5.4.224
linux linux kernel5.5 and later · before 5.10.154
linux linux kernel5.11 and later · before 5.15.61
linux linux kernel5.16 and later · before 5.18.18
linux linux kernel5.19 and later · before 5.19.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
- 4.20affected
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before 27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1baffected · git
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before 015ac18be7de25d17d6e5f1643cb3b60bfbe859eaffected · git
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before 622ef885a89ad04cfb76ee478fb44f051125d1f1affected · git
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before 925e6b6f82c9c80ab3c17acbde8d16f349da7d26affected · git
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before 1ec3f76a436d750fd5023caec5da0494fc2870d2affected · git
- dd2283f2605e3b3e9c61bcae844b34f2afa4813f and later · before a43cfc87caaf46710c8027a8c23b8a55f1078f19affected · git
- before 4.20not affected · semver
- 5.4.224 and later · up to and including 5.4.*not affected · semver
- 5.10.154 and later · up to and including 5.10.*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:12	linux	before 5.19.6-1	5.19.6-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-50236Sep 15, 2025 · iommu/mediatek: Fix crash on isr after kexec()
22Monitor
← EarlierCVE-2022-50239Sep 15, 2025 · cpufreq: qcom: fix writes in read-only memory region
28Monitor
Later →CVE-2022-50242Sep 15, 2025 · drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init()
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	015ac18be7de25d17d6e5f1643cb3b60bfbe859e	Vendor (CNA)
Linux Linux	1ec3f76a436d750fd5023caec5da0494fc2870d2	Vendor (CNA)
Linux Linux	27a594bc7a7c8238d239e3cdbcf2edfa3bbe9a1b	Vendor (CNA)
Linux Linux	622ef885a89ad04cfb76ee478fb44f051125d1f1	Vendor (CNA)
Linux Linux	925e6b6f82c9c80ab3c17acbde8d16f349da7d26	Vendor (CNA)
Linux Linux	a43cfc87caaf46710c8027a8c23b8a55f1078f19	Vendor (CNA)
debian:linux	5.19.6-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:10 PM UTC

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

References

git.kernel.org/stable/c/015ac18be7de25d17d6e5f1643cb3b60bfbe859e

Show all references (5 more)

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

All records