Quick answers
- Is CVE-2026-99206 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99206 being exploited in the wild.
- How severe is CVE-2026-99206?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Linux kernel All versions prior to the fix (introduced by commit e15b81f602ed).
- Is there a fix for CVE-2026-99206?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-99206 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99206?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A double-free vulnerability exists in iscsi_update_param_value() when concurrent configfs opens update the discovery AuthMethod parameter without synchronization. The fix adds proper locking with the discovery TPG access lock (iscsit_get_tpg/iscsit_put_tpg) to protect the lookup and replacement of authentication parameters, matching the pattern used elsewhere in the TPG configfs parameter update code.
Affected products
- Linux kernel All versions prior to the fix (introduced by commit e15b81f602ed)
Timeline
- 2026-10-28: disclosed
- 2026-08-11: other: Patch commit authored