netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 68983a354a655c35d3fb204489d383a2a051fda7 · < f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels
IDLETIMER revision 0 rules reuse existing timers by label and always call mod_timer() on timer->timer.
If the label was created first by revision 1 with XT_IDLETIMER_ALARM, the object uses alarm timer semantics and timer->timer is never initialized. Reusing that object from revision 0 causes mod_timer() on an uninitialized timer_list, triggering debugobjects warnings and possible panic when panic_on_warn=1.
Fix this by rejecting revision 0 rule insertion when an existing timer with the same label is of ALARM type.
From the CVE record · Linux
Linux netfilter's xt_IDLETIMER can reuse an ALARM timer label created by a revision 1 rule when inserting a revision 0 rule. This calls mod_timer() on an uninitialized timer, causing debugobjects warnings and a possible panic if panic_on_warn=1. Exploitation requires the ability to insert the affected rules; the input does not specify authentication requirements.
Engineers running Linux kernels with netfilter xt_IDLETIMER should check their systems; affected versions are not specified.