Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49607: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()

Noroxi assessment

Priority: Monitor (action score 18/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.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 17f5417194136517ee9bbd6511249e5310e5617c, 3.10, 3.3.

Low priority for now. Upgrade to Linux Linux 17f5417194136517ee9bbd6511249e5310e5617c, 3.10, 3.3 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: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() Yang Jihing reported a race between perf_event_set_output() and perf_mmap_close(): CPU1 CPU2 perf_mmap_close(e2) if (atomic_dec_and_test(&e2->rb->mmap_count)) // 1 - > 0 detach_rest = true ioctl(e1, IOC_SET_OUTPUT, e2) perf_event_set_output(e1, e2) ... list_for_each_entry_rcu(e, &e2->rb->event_list, rb_entry) ring_buffer_attach(e, NULL); // e1 isn't yet added and // therefore not detached ring_buffer_attach(e1, e2->rb) list_add_rcu(&e1->rb_entry, &e2->rb->event_list) After this; e1 is attached to an unmapped rb and a subsequent perf_mmap() will loop forever more: again: mutex_lock(&e->mmap_mutex); if (event->rb) { ... if (!atomic_inc_not_zero(&e->rb->mmap_count)) { ... mutex_unlock(&e->mmap_mutex); goto again; } } The loop in perf_mmap_close() holds e2->mmap_mutex, while the attach in perf_event_set_output() holds e1->mmap_mutex. As such there is no serialization to avoid this race. Change perf_event_set_output() to take both e1->mmap_mutex and e2->mmap_mutex to alleviate that problem. Additionally, have the loop in perf_mmap() detach the rb directly, this avoids having to wait for the concurrent perf_mmap_close() to get around to doing it to make progress.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-2022-49607

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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

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.

VendorProduct
linuxlinux 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.2.49 and later · before 3.3
  • linux linux kernel3.4.52 and later · before 3.5
  • linux linux kernel3.9.8 and later · before 4.9.325
  • linux linux kernel4.10 and later · before 4.14.290
  • linux linux kernel4.15 and later · before 4.19.254
  • linux linux kernel4.20 and later · before 5.4.208
  • linux linux kernel5.5 and later · before 5.10.134
  • linux linux kernel5.11 and later · before 5.15.58
  • linux linux kernel5.16 and later · before 5.18.15
  • linux linux kernel5.19

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

    • 2487f0db30527032c4d56fc2d0b1a240fe89fef8, 703197b61d05f5edae54bad3256901c5a5c8794c, c52217e88ae0f3a4ae00562d86e338f8f85969b4, 3.10affected
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before 3bbd868099287ff9027db59029b502fcfa2202a0affected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before f836f9ac95df15f1e0af4beb0ec20021e8c91998affected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before 17f5417194136517ee9bbd6511249e5310e5617caffected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before 98c3c8fd0d4c560e0f8335b79c407bbf7fc9462caffected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before 43128b3eee337824158f34da6648163d2f2fb937affected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before da3c256e2d0ebc87c7db0c605c9692b6f1722074affected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before a9391ff7a7c5f113d6f2bf6621d49110950de49caffected · git
    • 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b and later · before 68e3c69803dada336893640110cb87221bb01dcfaffected · git
    • 3.2.49 and later · before 3.3affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.16-15.18.16-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-49605Feb 26, 2025 · igc: Reinstate IGC_REMOVED logic and implement it properly
    22Monitor
  • ← EarlierCVE-2022-49606Feb 26, 2025 · RDMA/irdma: Fix sleep from invalid context BUG
    22Monitor
  • Later →CVE-2022-49608Feb 26, 2025 · pinctrl: ralink: Check for null return of devm_kcalloc
    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 Linux17f5417194136517ee9bbd6511249e5310e5617cVendor (CNA)
Linux Linux3.10Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux3.5Vendor (CNA)
Linux Linux3bbd868099287ff9027db59029b502fcfa2202a0Vendor (CNA)
Linux Linux43128b3eee337824158f34da6648163d2f2fb937Vendor (CNA)
Linux Linux68e3c69803dada336893640110cb87221bb01dcfVendor (CNA)
Linux Linux98c3c8fd0d4c560e0f8335b79c407bbf7fc9462cVendor (CNA)
Linux Linuxa9391ff7a7c5f113d6f2bf6621d49110950de49cVendor (CNA)
Linux Linuxda3c256e2d0ebc87c7db0c605c9692b6f1722074Vendor (CNA)
Linux Linuxf836f9ac95df15f1e0af4beb0ec20021e8c91998Vendor (CNA)
debian:linux5.18.16-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records