SECUFOCUSNOW
Home›CVE index›CVE-2026-53075
Review reviewHigh

CVE-2026-53075

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls /dev/ppp open is currently authorized against file->f_cred->user_ns, while unattached administrative ioctls operate on current->nsproxy->net_ns. As a result, a local unprivileged user can create a new user namespace with CLONE_NEWUSER, gain CAP_NET_ADMIN only in that new user namespace, and still issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited network namespace. Require CAP_NET_ADMIN in the user namespace that owns the target network n...

CVSS
8.8
EPSS
0.25%
16.5% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.25%
Technical severityCVSS 8.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls /dev/ppp open is currently authorized against file->f_cred->user_ns, while unattached administrative ioctls operate on current->nsproxy->net_ns. As a result, a local unprivileged user can create a new user namespace with CLONE_NEWUSER, gain CAP_NET_ADMIN only in that new user namespace, and still issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited network namespace. Require CAP_NET_ADMIN in the user namespace that owns the target network n...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 273ec51dd7ceaa76e038875d85061ec856d8905e < c9edd90c57ae23692fff6b049fdfa4572a9fd532, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 5080e188c914110034bbc569d5cfa2f06204681d, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 67e901e28d177ac9a9bed76d69ce3471e704a89e, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 954745d0223e7caec917c0b2d1a889ff56fa6e54, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 3b2c2157dc2afc5c17cd7238afefca92f1ef330e, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 5013be175c7ffd8b39efbc3c9c4db5b10b85fea8, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 1a8a51ce85075a56a743b6f142606dd2696a391c, >= 273ec51dd7ceaa76e038875d85061ec856d8905e < 2bb6379416fd19f44c3423a00bfd8626259f6067, >= 2.6.30, >= 2.6.30 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE
Not available