nfc: fix memory leak of se_io context in nfc_genl_se_io
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5ce3f32b5264b337bfd13a780452a17705307725 · < b2036a252381949d3b743a3de069324ae3028a57| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfc: fix memory leak of se_io context in nfc_genl_se_io
The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfc_genl_se_io and supposed to be eventually freed in se_io_cb callback function. However, there are several error paths where the bwi_timer is not charged to call se_io_cb later, and the cb_context is leaked.
The patch proposes to free the cb_context explicitly on those error paths.
At the moment we can't simply check 'dev->ops->se_io()' return value as it may be negative in both cases: when the timer was charged and was not.
From the CVE record · Linux
The Linux kernel's nfc_genl_se_io can leak callback context on error paths where its timer will not invoke the cleanup callback. An attacker who can trigger those paths could cause memory to leak; the input does not specify network or local access, authentication, or user-interaction requirements.
Operators running the Linux kernel should check their exposure; affected versions are not specified.