Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50341: cifs: fix oops during encryption

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.11% (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 a13e51760703f71c25d5fc1f4a62dfa4b0cc80e9, bf0543b93740916ee91956f9a63da6fc0d79daaa, e8d16a54842d609fd4a3ed2d81d4333d6329aa94.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux a13e51760703f71c25d5fc1f4a62dfa4b0cc80e9, bf0543b93740916ee91956f9a63da6fc0d79daaa, e8d16a54842d609fd4a3ed2d81d4333d6329aa94 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: cifs: fix oops during encryption When running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel write to read-only memory at virtual address ffff0001221cf000 Mem abort info: ESR = 0x9600004f EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x0f: level 3 permission fault Data abort info: ISV = 0, ISS = 0x0000004f CM = 0, WnR = 1 swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000294f3000 [ffff0001221cf000] pgd=18000001ffff8003, p4d=18000001ffff8003, pud=18000001ff82e003, pmd=18000001ff71d003, pte=00600001221cf787 Internal error: Oops: 9600004f [#1] PREEMPT SMP ... pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) pc : __memcpy+0x40/0x230 lr : scatterwalk_copychunks+0xe0/0x200 sp : ffff800014e92de0 x29: ffff800014e92de0 x28: ffff000114f9de80 x27: 0000000000000008 x26: 0000000000000008 x25: ffff800014e92e78 x24: 0000000000000008 x23: 0000000000000001 x22: 0000040000000000 x21: ffff000000000000 x20: 0000000000000001 x19: ffff0001037c4488 x18: 0000000000000014 x17: 235e1c0d6efa9661 x16: a435f9576b6edd6c x15: 0000000000000058 x14: 0000000000000001 x13: 0000000000000008 x12: ffff000114f2e590 x11: ffffffffffffffff x10: 0000040000000000 x9 : ffff8000105c3580 x8 : 2e9413b10000001a x7 : 534b4410fb86b005 x6 : 534b4410fb86b005 x5 : ffff0001221cf008 x4 : ffff0001037c4490 x3 : 0000000000000001 x2 : 0000000000000008 x1 : ffff0001037c4488 x0 : ffff0001221cf000 Call trace: __memcpy+0x40/0x230 scatterwalk_map_and_copy+0x98/0x100 crypto_ccm_encrypt+0x150/0x180 crypto_aead_encrypt+0x2c/0x40 crypt_message+0x750/0x880 smb3_init_transform_rq+0x298/0x340 smb_send_rqst.part.11+0xd8/0x180 smb_send_rqst+0x3c/0x100 compound_send_recv+0x534/0xbc0 smb2_query_info_compound+0x32c/0x440 smb2_set_ea+0x438/0x4c0 cifs_xattr_set+0x5d4/0x7c0 This is because in scatterwalk_copychunks(), we attempted to write to a buffer (@sign) that was allocated in the stack (vmalloc area) by crypt_message() and thus accessing its remaining 8 (x2) bytes ended up crossing a page boundary. To simply fix it, we could just pass @sign kmalloc'd from crypt_message() and then we're done. Luckily, we don't seem to pass any other vmalloc'd buffers in smb_rqst::rq_iov... Instead, let's map the correct pages and offsets from vmalloc buffers as well in cifs_sg_set_buf() and then avoiding such oopses.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 16, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 1th 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.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

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.

Follow CVE-2022-50341

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 kernelbefore 5.4.229
  • linux linux kernel5.5 and later · before 5.10.163
  • linux linux kernel5.11 and later · before 5.15.87
  • linux linux kernel5.16 and later · before 6.0.16
  • linux linux kernel6.1 and later · before 6.1.1

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.11affected
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before e8e2861cc3258dbe407d01ea8c59bb5a53132301affected · git
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before fe6ea044c4f05706cb71040055b1c70c6c8275e0affected · git
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before bf0543b93740916ee91956f9a63da6fc0d79daaaaffected · git
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before a13e51760703f71c25d5fc1f4a62dfa4b0cc80e9affected · git
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before e8d16a54842d609fd4a3ed2d81d4333d6329aa94affected · git
    • 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 and later · before f7f291e14dde32a07b1f0aa06921d28f875a7b54affected · git
    • before 4.11not affected · semver
    • 5.4.229 and later · up to and including 5.4.*not affected · semver
    • 5.10.163 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1
Red Hat:enterprise_linux:8::baseosbpftoolbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseosbpftool-debuginfobefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernelbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-abi-stablelistsbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-corebefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debugbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-corebefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-debuginfobefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-develbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modulesbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debug-modules-extrabefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfobefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-develbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-docbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modulesbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-modules-extrabefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-toolsbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-debuginfobefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10
Red Hat:enterprise_linux:8::baseoskernel-tools-libsbefore 0:4.18.0-553.27.1.el8_100:4.18.0-553.27.1.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50339Sep 16, 2025 · Bluetooth: avoid hci_dev_test_and_set_flag() in mgmt_init_hdev()
    28Monitor
  • ← EarlierCVE-2022-50340Sep 16, 2025 · media: vimc: Fix wrong function called when vimc_init() fails
    22Monitor
  • Later →CVE-2022-50342Sep 16, 2025 · floppy: Fix memory leak in do_floppy_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 / packageFixed versionSource
Linux Linuxa13e51760703f71c25d5fc1f4a62dfa4b0cc80e9Vendor (CNA)
Linux Linuxbf0543b93740916ee91956f9a63da6fc0d79daaaVendor (CNA)
Linux Linuxe8d16a54842d609fd4a3ed2d81d4333d6329aa94Vendor (CNA)
Linux Linuxe8e2861cc3258dbe407d01ea8c59bb5a53132301Vendor (CNA)
Linux Linuxf7f291e14dde32a07b1f0aa06921d28f875a7b54Vendor (CNA)
Linux Linuxfe6ea044c4f05706cb71040055b1c70c6c8275e0Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage 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.
  • 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

Show all references (5 more)

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

All records