afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server
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.21% (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 b537a3c21775075395af475dcc6ef212fcf29db8, e66fc460d6dcf85cf12288e133a081205aebcd97.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux b537a3c21775075395af475dcc6ef212fcf29db8, e66fc460d6dcf85cf12288e133a081205aebcd97 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: afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and Linux's afs client switches between them when talking to a non-YFS server if the read size, the file position or the sum of the two have the upper 32 bits set of the 64-bit value. This is a problem, however, since the file position and length fields of FS.FetchData are *signed* 32-bit values. Fix this by capturing the capability bits obtained from the fileserver when it's sent an FS.GetCapabilities RPC, rather than just discarding them, and then picking out the VICED_CAPABILITY_64BITFILES flag. This can then be used to decide whether to use FS.FetchData or FS.FetchData64 - and also FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to switch on the parameter values. This capabilities flag could also be used to limit the maximum size of the file, but all servers must be checked for that. Note that the issue does not exist with FS.StoreData - that uses *unsigned* 32-bit values. It's also not a problem with Auristor servers as its YFS.FetchData64 op uses unsigned 64-bit values. This can be tested by cloning a git repo through an OpenAFS client to an OpenAFS server and then doing "git status" on it from a Linux afs client[1]. Provided the clone has a pack file that's in the 2G-4G range, the git status will show errors like: error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index error: packfile .git/objects/pack/pack-5e813c51d12b6847bbc0fcd97c2bca66da50079c.pack does not match index This can be observed in the server's FileLog with something like the following appearing: Sun Aug 29 19:31:39 2021 SRXAFS_FetchData, Fid = 2303380852.491776.3263114, Host 192.168.11.201:7001, Id 1001 Sun Aug 29 19:31:39 2021 CheckRights: len=0, for host=192.168.11.201:7001 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: Pos 18446744071815340032, Len 3154 Sun Aug 29 19:31:39 2021 FetchData_RXStyle: file size 2400758866 ... Sun Aug 29 19:31:40 2021 SRXAFS_FetchData returns 5 Note the file position of 18446744071815340032. This is the requested file position sign-extended.
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-787
Report tools
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%
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.1
- 1.6 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.22 and later · before 5.14.9
- linux linux kernel5.15
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.22affected
- b9b1f8d5930a813879278d0cbfc8c658d6a038dc and later · before e66fc460d6dcf85cf12288e133a081205aebcd97affected · git
- b9b1f8d5930a813879278d0cbfc8c658d6a038dc and later · before b537a3c21775075395af475dcc6ef212fcf29db8affected · git
- before 2.6.22not affected · semver
- 5.14.9 and later · up to and including 5.14.*not affected · semver
- 5.15 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.9-1 | 5.14.9-1 |
| openSUSE:Leap 15.5 | dtb-aarch64 | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-64kb | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.57.1 | 5.14.21-150500.33.57.1 |
| openSUSE:Leap 15.5 | kernel-debug | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-default | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-default-base | before 5.14.21-150500.55.68.1.150500.6.31.1 | 5.14.21-150500.55.68.1.150500.6.31.1 |
| openSUSE:Leap 15.5 | kernel-docs | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-kvmsmall | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-obs-build | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-obs-qa | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-rt | before 5.14.21-150500.13.58.1 | 5.14.21-150500.13.58.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.58.1 | 5.14.21-150500.13.58.1 |
| openSUSE:Leap 15.5 | kernel-source | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.57.1 | 5.14.21-150500.33.57.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.58.1 | 5.14.21-150500.13.58.1 |
| openSUSE:Leap 15.5 | kernel-syms | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.57.1 | 5.14.21-150500.33.57.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.58.1 | 5.14.21-150500.13.58.1 |
| openSUSE:Leap 15.5 | kernel-zfcpdump | before 5.14.21-150500.55.68.1 | 5.14.21-150500.55.68.1 |
| openSUSE:Leap Micro 5.3 | kernel-default | before 5.14.21-150400.24.122.2 | 5.14.21-150400.24.122.2 |
| openSUSE:Leap Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.122.2.150400.24.58.2 | 5.14.21-150400.24.122.2.150400.24.58.2 |
| openSUSE:Leap Micro 5.3 | kernel-rt | before 5.14.21-150400.15.82.1 | 5.14.21-150400.15.82.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.122.2 | 5.14.21-150400.24.122.2 |
+27
Same product
linux: all recordsOther 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- 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 haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47364May 21, 2024 · comedi: Fix memory leak in compat_insnlist()22Monitor
- ← EarlierCVE-2021-47365May 21, 2024 · In the Linux kernel, the following vulnerability has been resolved:
afs: Fix page leak
There's a loop in afs_extend_writeback() that adds 22Monitor
- Later →CVE-2021-47367May 21, 2024 · virtio-net: fix pages leaking when building skb in big mode22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | b537a3c21775075395af475dcc6ef212fcf29db8 | Vendor (CNA) |
| Linux Linux | e66fc460d6dcf85cf12288e133a081205aebcd97 | Vendor (CNA) |
| debian:linux | 5.14.9-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 5.14.21-150500.55.68.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-64kb | 5.14.21-150500.55.68.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150500.33.57.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-debug | 5.14.21-150500.55.68.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-default | 5.14.21-150400.24.122.2 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-default-base | 5.14.21-150400.24.122.2.150400.24.58.2 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150500.13.58.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.58.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150500.33.57.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.58.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150500.33.57.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.58.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.122.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-azure | 5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.122.2 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.122.2.150400.24.58.2 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_27 | 1-150400.9.3.2 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_16 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-rt_debug | 5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.58.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms-azure | 5.14.21-150500.33.57.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 5.14.21-150500.13.58.1 · SUSE:Real Time Module 15 SP5 | Package 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.
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0519 · May 22, 2024(Linux Kernel Güncellemesi)
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)
CWE-787 · Out-of-bounds WriteCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.