cifs: Fix connections leak when tlink setup failed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cifs: Fix connections leak when tlink setup failed
If the tlink setup failed, lost to put the connections, then the module refcnt leak since the cifsd kthread not exit.
Also leak the fscache info, and for next mount with fsc, it will print the follow errors: CIFS: Cache volume key already in use (cifs,127.0.0.1:445,TEST)
Let's check the result of tlink setup, and do some cleanup.
From the CVE record · Linux
The Linux kernel’s cifs code fails to release connections when tlink setup fails, leaking a module reference and fscache information. A subsequent mount using fscache can report that the cache volume key is already in use. The input does not specify attacker access or user-interaction requirements.
Engineers running Linux systems that mount CIFS shares should check their kernel versions; affected versions are not specified.