← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-43362

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-43362

Key Details

CVECVE-2026-43362
CVSS Score / Version
8.1 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is required; scope is unchanged; confidentiality impact is none; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-787 (Out-of-bounds Write)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix in-place encryption corruption in SMB2_write()

SMB2_write() places write payload in iov[1..n] as part of rq_iov.

smb3_init_transform_rq() pointer-shares rq_iov, so crypt_message()

encrypts iov[1] in-place, replacing the original plaintext with

ciphertext. On a replayable error, the retry sends the same iov[1]

which now contains ciphertext instead of the original data,

resulting in corruption.

The corruption is most likely to be observed when connections are

unstable, as reconnects trigger write retries that re-send the

already-encrypted data.

This affects SFU mknod, MF symlinks, etc. On kernels before

6.10 (prior to the netfs conversion), sync writes also used

this path and were similarly affected. The async write path

wasn't unaffected as it uses rq_iter which gets deep-copied.

Fix by moving the write payload into rq_iter via iov_iter_kvec(),

so smb3_init_transform_rq() deep-copies it before encryption. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-43362
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-43362
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.