CVE-2026-31392smb: client: fix krb5 mount with username option
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix krb5 mount with username option Customer reported that some of their krb5 mounts were failing against a single server as the client was trying to mount the shares with wrong credentials. It turned out the client was reusing SMB session from first mount to try mounting the other shares, even though a different username= option had been specified to the other mounts. By using username mount option along with sec=krb5 to search for principals from keytab is supported by cifs.upcall(8) since cifs-utils-4.8. So fix this by matching username mount option in match_session() even with Kerberos. For example, the second mount below should fail with -ENOKEY as there is no 'foobar' principal in keytab (/etc/krb5.keytab). The client ends up reusing SMB session from first mount to perform the second one, which is wrong. ``` $ ktutil ktutil: add_entry -password -p testuser -k 1 -e aes256-cts Password for testuser@ZELDA.TEST: ktutil: write_kt /etc/krb5.keytab ktutil: quit $ klist -ke Keytab name: FILE:/etc/krb5.keytab KVNO Principal ---- ---------------------------------------------------------------- 1 testuser@ZELDA.TEST (aes256-cts-hmac-sha1-96) $ mount.cifs //w22-root2/scratch /mnt/1 -o sec=krb5,username=testuser $ mount.cifs //w22-root2/scratch /mnt/2 -o sec=krb5,username=foobar $ mount -t cifs | grep -Po 'username=\K\w+' testuser testuser ```
- CVSS
- 8.1 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before fd4547830720647d4af02ee50f883c4b1cca06e4; from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before 9229709ec8bf85ae7ca53aeee9aa14814cdc1bd2; from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before d33cbf0bf8979d779900da9be2505d68d9d8da25; from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before 9ee803bfdba0cf739038dbdabdd4c02582c8f2b2; from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before 6e9ff1eb7feedcf46ff2d0503759960ab58e7775; from 4ff67b720c02c36e54d55b88c2931879b7db1cd2 before 12b4c5d98cd7ca46d5035a57bcd995df614c14e1; 223c7f082d2836ac719b3b228bdcfab35e5e5330; 88720224330a655ab6268e20109b65b11cfd7f6a; and 2 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 2.6.32.44 before 2.6.33; from 2.6.34.12 before 2.6.35; from 2.6.36 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.78; from 6.13 before 6.18.20; from 6.19 before 6.19.10; 7.0; and 3 more ranges | NVD |
References
- https://git.kernel.org/stable/c/fd4547830720647d4af02ee50f883c4b1cca06e4patch
- https://git.kernel.org/stable/c/9229709ec8bf85ae7ca53aeee9aa14814cdc1bd2patch
- https://git.kernel.org/stable/c/d33cbf0bf8979d779900da9be2505d68d9d8da25patch
- https://git.kernel.org/stable/c/9ee803bfdba0cf739038dbdabdd4c02582c8f2b2patch
- https://git.kernel.org/stable/c/6e9ff1eb7feedcf46ff2d0503759960ab58e7775patch
- https://git.kernel.org/stable/c/12b4c5d98cd7ca46d5035a57bcd995df614c14e1patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.