pnode: terminate at peers of source
In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propagation mount tree headed by @dest_mnt. Unfortunately it contains a bug where it fails to terminate at peers of @source_mnt when looking up copies of the source mount that become masters for copies of the source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference. Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces it is available to unprivileged users. While fixing this bug we've gotten confused multiple times due to unclear terminology or missing concepts. So let's start this with some clarifications: * The terms "master" or "peer" denote a shared mount. A shared mount belongs to a peer group. * A peer group is a set of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer group id. The peers in a peer group can be reached via @shared_mnt->mnt_share. * The terms "slave mount" or "dependent mount" denote a mount that receives propagation from a peer in a peer group. IOW, shared mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list. * The term "master mount" denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a peer group. The term "master mount" - or "master" for short - is mostly used when talking in the context of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the closest peer group a slave mount receives propagation from. The master mount of a slave can be identified via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group. * Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the ->mnt_slave_lists of all peers in a peer group have to be walked. * Slave mounts point to a peer in the closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with these peers they form a propagation group (see below). The closest peer group can thus be identified through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list. IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---
- Published
- Sep 15, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 4th percentile
- CWE
- CWE-476
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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%
Affected systems
| 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 kernel3.14.3 and later · before 4.9.337
- linux linux kernel4.10 and later · before 4.14.303
- linux linux kernel4.15 and later · before 4.19.270
- linux linux kernel4.20 and later · before 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.17
- linux linux kernel6.1 and later · before 6.1.3
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
- fc7b1646bf29f722277bdd19551e01420ce9da8f, 3.15affected
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before cad0d17fb2b0540180ab59e2cd48ad348cc1ee4caffected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before cc997490be65da0af8c75a6244fc80bb66c53ce0affected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before 7f57df69de7f05302fad584eb8e3f34de39e0311affected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before 2dae4211b579ce98985876a73a78466e285238ffaffected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before b591b2919d018ef91b4a9571edca94105bcad3dfaffected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before c24cc476acd8bccb5af54849aac5e779d8223bf5affected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before e7c9f10c44a8919cd8bbd51b228c84d0caf7d518affected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before 784a4f995ee24460aa72e00b085612fad57ebce5affected · git
- f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68 and later · before 11933cf1d91d57da9e5c53822a540bbdc2656c16affected · git
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 6.1.4-1 | 6.1.4-1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-64kb | before 5.3.18-150300.59.229.3 | 5.3.18-150300.59.229.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-default-base | before 5.3.18-150300.59.229.3.150300.18.136.3 | 5.3.18-150300.59.229.3.150300.18.136.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-docs | before 5.3.18-150300.59.229.2 | 5.3.18-150300.59.229.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-obs-build | before 5.3.18-150300.59.229.3 | 5.3.18-150300.59.229.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-preempt | before 5.3.18-150300.59.229.3 | 5.3.18-150300.59.229.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-source | before 5.3.18-150300.59.229.3 | 5.3.18-150300.59.229.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-syms | before 5.3.18-150300.59.229.1 | 5.3.18-150300.59.229.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.187.3 | 5.14.21-150400.24.187.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-docs | before 5.14.21-150400.24.187.1 | 5.14.21-150400.24.187.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-obs-build | before 5.14.21-150400.24.187.3 | 5.14.21-150400.24.187.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-source | before 5.14.21-150400.24.187.3 | 5.14.21-150400.24.187.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-syms | before 5.14.21-150400.24.187.1 | 5.14.21-150400.24.187.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-64kb | before 5.14.21-150500.55.130.3 | 5.14.21-150500.55.130.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-docs | before 5.14.21-150500.55.130.1 | 5.14.21-150500.55.130.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-obs-build | before 5.14.21-150500.55.130.3 | 5.14.21-150500.55.130.3 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-syms | before 5.14.21-150500.55.130.1 | 5.14.21-150500.55.130.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.280.1 | 4.12.14-122.280.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_74 | before 1-8.5.1 | 1-8.5.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-default | before 5.3.18-150300.59.229.3 | 5.3.18-150300.59.229.3 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_64 | before 1-150300.7.3.3 | 1-150300.7.3.3 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_47 | before 1-150400.9.3.3 | 1-150400.9.3.3 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_33 | before 1-150500.11.3.3 | 1-150500.11.3.3 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-rt | before 5.3.18-150300.229.2 | 5.3.18-150300.229.2 |
+15
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
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 11933cf1d91d57da9e5c53822a540bbdc2656c16 | Vendor (CNA) |
| Linux Linux | 2dae4211b579ce98985876a73a78466e285238ff | Vendor (CNA) |
| Linux Linux | 3.15 | Vendor (CNA) |
| Linux Linux | 784a4f995ee24460aa72e00b085612fad57ebce5 | Vendor (CNA) |
| Linux Linux | 7f57df69de7f05302fad584eb8e3f34de39e0311 | Vendor (CNA) |
| Linux Linux | b591b2919d018ef91b4a9571edca94105bcad3df | Vendor (CNA) |
| Linux Linux | c24cc476acd8bccb5af54849aac5e779d8223bf5 | Vendor (CNA) |
| Linux Linux | cad0d17fb2b0540180ab59e2cd48ad348cc1ee4c | Vendor (CNA) |
| Linux Linux | cc997490be65da0af8c75a6244fc80bb66c53ce0 | Vendor (CNA) |
| Linux Linux | e7c9f10c44a8919cd8bbd51b228c84d0caf7d518 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150500.55.130.3 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.280.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150500.55.130.3.150500.6.63.3 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150500.55.130.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_64 | 1-150300.7.3.3 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_33 | 1-150500.11.3.3 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150500.55.130.3 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-preempt | 5.3.18-150300.59.229.3 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.280.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.280.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150500.55.130.3 · SUSE:Linux Enterprise Server 15 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_74 | 1-8.5.1 · SUSE:Linux Enterprise Live Patching 12 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).
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-476 · NULL Pointer DereferenceCVSS 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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/11933cf1d91d57da9e5c53822a540bbdc2656c16
- git.kernel.org/stable/c/2dae4211b579ce98985876a73a78466e285238ff
- git.kernel.org/stable/c/784a4f995ee24460aa72e00b085612fad57ebce5
- git.kernel.org/stable/c/7f57df69de7f05302fad584eb8e3f34de39e0311
- git.kernel.org/stable/c/b591b2919d018ef91b4a9571edca94105bcad3df
- git.kernel.org/stable/c/c24cc476acd8bccb5af54849aac5e779d8223bf5
- git.kernel.org/stable/c/cad0d17fb2b0540180ab59e2cd48ad348cc1ee4c
- git.kernel.org/stable/c/cc997490be65da0af8c75a6244fc80bb66c53ce0
- git.kernel.org/stable/c/e7c9f10c44a8919cd8bbd51b228c84d0caf7d518
Vendor advisories and official records. Exploit/PoC links are deliberately left out.