Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49767: 9p/trans_fd: always use O_NONBLOCK read/write

Noroxi assessment

Priority: Monitor (action score 22/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.20% (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 0b5e6bd72b8171364616841603a70e4ba9837063, 0e07032b4b4724b8ad1003698cb81083c1818999, 5af16182c5639349415118e9e9aecd8355f7a08b.

Low priority for now. Upgrade to Linux Linux 0b5e6bd72b8171364616841603a70e4ba9837063, 0e07032b4b4724b8ad1003698cb81083c1818999, 5af16182c5639349415118e9e9aecd8355f7a08b 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: 9p/trans_fd: always use O_NONBLOCK read/write syzbot is reporting hung task at p9_fd_close() [1], for p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is failing to interrupt already started kernel_read() from p9_fd_read() from p9_read_work() and/or kernel_write() from p9_fd_write() from p9_write_work() requests. Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not need to interrupt kernel_read()/kernel_write(). However, since p9_fd_open() does not set O_NONBLOCK flag, but pipe blocks unless signal is pending, p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when the file descriptor refers to a pipe. In other words, pipe file descriptor needs to be handled as if socket file descriptor. We somehow need to interrupt kernel_read()/kernel_write() on pipes. A minimal change, which this patch is doing, is to set O_NONBLOCK flag from p9_fd_open(), for O_NONBLOCK flag does not affect reading/writing of regular files. But this approach changes O_NONBLOCK flag on userspace- supplied file descriptors (which might break userspace programs), and O_NONBLOCK flag could be changed by userspace. It would be possible to set O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked, but still remains small race window for clearing O_NONBLOCK flag. If we don't want to manipulate O_NONBLOCK flag, we might be able to surround kernel_read()/kernel_write() with set_thread_flag(TIF_SIGPENDING) and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are processed by kernel threads which process global system_wq workqueue, signals could not be delivered from remote threads when p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is called. Therefore, calling set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be needed if we count on signals for making kernel_read()/kernel_write() non-blocking. [Dominique: add comment at Christian's suggestion]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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

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.

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 kernelbefore 4.9.334
  • linux linux kernel4.10 and later · before 4.14.300
  • linux linux kernel4.15 and later · before 4.19.267
  • linux linux kernel4.20 and later · before 5.4.225
  • linux linux kernel5.5 and later · before 5.10.156
  • linux linux kernel5.11 and later · before 5.15.80
  • linux linux kernel5.16 and later · before 6.0.10

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

    • 2.6.17affected
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before 0b5e6bd72b8171364616841603a70e4ba9837063affected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before 9f8554615df668e4bf83294633ee9d232b28ce45affected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before 7abf40f06a76c0dff42eada10597917e9776fbd4affected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before b1ad04da7fe4515e2ce2d5f2dcab3b5b6d45614baffected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before a8e2fc8f7b41fa9d9ca5f624f4e4d34fce5b40a9affected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before 0e07032b4b4724b8ad1003698cb81083c1818999affected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before 5af16182c5639349415118e9e9aecd8355f7a08baffected · git
    • 27979bb2ff748613dba96ae66392a76fb0678527 and later · before ef575281b21e9a34dfae544a187c6aac2ae424a9affected · git
    • before 2.6.17not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.10-16.0.10-1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.207.1.150300.18.124.15.3.18-150300.59.207.1.150300.18.124.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-sourcebefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-64kbbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-docsbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-obs-buildbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-symsbefore 5.14.21-150500.55.103.15.14.21-150500.55.103.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.207.15.3.18-150300.59.207.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_58before 1-150300.7.3.11-150300.7.3.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_41before 1-150400.9.3.11-150400.9.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_26before 1-150500.11.3.11-150500.11.3.1
SUSE:Linux Enterprise Micro 5.3kernel-defaultbefore 5.14.21-150400.24.167.15.14.21-150400.24.167.1
SUSE:Linux Enterprise Micro 5.3kernel-default-basebefore 5.14.21-150400.24.167.1.150400.24.84.15.14.21-150400.24.167.1.150400.24.84.1
SUSE:Linux Enterprise Micro 5.3kernel-rtbefore 5.14.21-150400.15.121.15.14.21-150400.15.121.1

+9

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-49765May 1, 2025 · net/9p: use a dedicated spinlock for trans_fd
    22Monitor
  • ← EarlierCVE-2022-49766May 1, 2025 · netlink: Bounds-check struct nlmsgerr creation
    22Monitor
  • Later →CVE-2022-49768May 1, 2025 · 9p: trans_fd/p9_conn_cancel: drop client lock earlier
    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 Linux0b5e6bd72b8171364616841603a70e4ba9837063Vendor (CNA)
Linux Linux0e07032b4b4724b8ad1003698cb81083c1818999Vendor (CNA)
Linux Linux5af16182c5639349415118e9e9aecd8355f7a08bVendor (CNA)
Linux Linux7abf40f06a76c0dff42eada10597917e9776fbd4Vendor (CNA)
Linux Linux9f8554615df668e4bf83294633ee9d232b28ce45Vendor (CNA)
Linux Linuxa8e2fc8f7b41fa9d9ca5f624f4e4d34fce5b40a9Vendor (CNA)
Linux Linuxb1ad04da7fe4515e2ce2d5f2dcab3b5b6d45614bVendor (CNA)
Linux Linuxef575281b21e9a34dfae544a187c6aac2ae424a9Vendor (CNA)
debian:linux6.0.10-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-default-base5.14.21-150500.55.103.1.150500.6.49.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-docs5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_581-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_261-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-obs-build5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-rt5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-source-rt5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:kernel-syms5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Server 15 SP5-LTSSPackage 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.

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

All records