CVE-2022-48668: smb3: fix temporary data corruption in collapse range
In the Linux kernel, the following vulnerability has been resolved:
smb3: fix temporary data corruption in collapse range
collapse range doesn't discard the affected cached region
so can risk temporarily corrupting the file data. This
fixes xfstest generic/031
I also decided to merge a minor cleanup to this into the same patch
(avoiding rereading inode size repeatedly unnecessarily) to make it
clearer.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause temporary file data corruption when SMB3 collapse-range handling leaves stale cached data in place. The sources describe a correctness and data-integrity problem, not confirmed code execution or privilege escalation.
Executive priority
Treat this as a data-integrity maintenance risk. Prioritize patching for systems handling important files over SMB3, but the provided evidence does not justify emergency response absent business-critical exposure.
Technical view
The SMB3 collapse range path failed to discard the affected cached region, risking temporary corruption of file data. The kernel fix invalidates or handles the cache correctly and resolves xfstest generic/031. Public sources provide no CVSS, CWE, or exploitation details.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or commit ranges and using SMB3/CIFS file operations where collapse range is exercised. Systems not using this code path are less likely to see impact.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV in the source bundle. Evidence supports a kernel data-corruption bug, but not weaponized exploitation.
Researcher notes
Key uncertainty is impact breadth: sources describe temporary data corruption and a regression-test fix, but provide no CVSS, CWE, exploitability analysis, or affected distribution matrix. Validate by kernel lineage and vendor backport status.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
Check vendor kernel advisories for backported fixes before assuming version numbers are sufficient.
Prioritize hosts that mount or serve critical workflows over SMB3/CIFS.
Avoid manual kernel patch assumptions without confirming the exact vendor build includes the fix.
Validation and detection
Inventory Linux kernel versions and vendor build identifiers on exposed systems.
Confirm whether systems use SMB3/CIFS workloads that could exercise collapse range.
Verify the kernel includes stable commits 49523a473220 or fa30a81f255a.
Run relevant filesystem regression testing, including generic/031, in non-production where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48668 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.