<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - nft list ruleset – infinite memory use"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1222">1222</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>nft list ruleset – infinite memory use
</td>
</tr>
<tr>
<th>Product</th>
<td>nftables
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86_64
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5
</td>
</tr>
<tr>
<th>Component</th>
<td>nft
</td>
</tr>
<tr>
<th>Assignee</th>
<td>pablo@netfilter.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>grawity@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>When this specific rule is inserted, trying to view it using `nft list ruleset`
causes the nft client to start allocating infinite amounts of RAM:
---
table inet filter {
chain input {
ct original ip daddr {1.2.3.4} accept
}
}
---
(The {set} is important – a standalone address doesn't cause this issue.)
nft debug output ends with:
---
...
Evaluate list
list ruleset
^^^^^^^^^^^^^
inet filter input 2
[ ct load l3protocol => reg 1 ]
[ cmp eq reg 1 0x00000002 ]
[ ct load dst => reg 1 , dir original ]
[ lookup reg 1 set __set0 0x0 ]
[ immediate reg 0 accept ]
<begins eating memory at this point>
---
nftables 0.8.1
libnftnl 1.0.9
linux 4.9.78, 4.13.13</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>