<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/Documentation/process/threat-model.rst, branch master</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=master</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2026-05-14T12:23:44Z</updated>
<entry>
<title>docs: threat-model: don't limit root capabilities to CAP_SYS_ADMIN</title>
<updated>2026-05-14T12:23:44Z</updated>
<author>
<name>Jonathan Corbet</name>
<email>corbet@lwn.net</email>
</author>
<published>2026-05-13T20:58:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f2e65e4e5b4b4b9ecf43f03c3fdbe8c9a8a43a9e'/>
<id>urn:sha1:f2e65e4e5b4b4b9ecf43f03c3fdbe8c9a8a43a9e</id>
<content type='text'>
The threat-model document says that only users with CAP_SYS_ADMIN can carry
out a number of admin-level tasks, but there are numerous capabilities that
can confer that sort of power.  Generalize the text slightly to make it
clear that CAP_SYS_ADMIN is not the only all-powerful capability.

Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: security-bugs: add a link to the threat-model documentation</title>
<updated>2026-05-14T12:23:06Z</updated>
<author>
<name>Jonathan Corbet</name>
<email>corbet@lwn.net</email>
</author>
<published>2026-05-13T20:51:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=561458db0d6b08b4e4956c6e4456d7781b18676f'/>
<id>urn:sha1:561458db0d6b08b4e4956c6e4456d7781b18676f</id>
<content type='text'>
Rather than make readers search for this document, just a link to it where
it is referenced.

(While I was at it, I removed the unused and unneeded _threatmodel label
from the top of threat-model.rst).

Acked-by: Willy Tarreau &lt;w@1wt.eu&gt;
Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>Documentation: security-bugs: explain what is and is not a security bug</title>
<updated>2026-05-12T17:09:14Z</updated>
<author>
<name>Willy Tarreau</name>
<email>w@1wt.eu</email>
</author>
<published>2026-05-09T09:47:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a03ef333fbd6cd861c8457c3d055ee3643a9baad'/>
<id>urn:sha1:a03ef333fbd6cd861c8457c3d055ee3643a9baad</id>
<content type='text'>
The use of automated tools to find bugs in random locations of the kernel
induces a raise of security reports even if most of them should just be
reported as regular bugs. This patch is an attempt at drawing a line
between what qualifies as a security bug and what does not, hoping to
improve the situation and ease decision on the reporter's side.

It defers the enumeration to a new file, threat-model.rst, that tries
to enumerate various classes of issues that are and are not security
bugs. This should permit to more easily update this file for various
subsystem-specific rules without having to revisit the security bug
reporting guide.

Cc: Greg KH &lt;gregkh@linuxfoundation.org&gt;
Cc: Leon Romanovsky &lt;leon@kernel.org&gt;
Suggested-by: Leon Romanovsky &lt;leon@kernel.org&gt;
Suggested-by: Greg KH &lt;gregkh@linuxfoundation.org&gt;
Reviewed-by: Leon Romanovsky &lt;leon@kernel.org&gt;
Reviewed-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;
Signed-off-by: Willy Tarreau &lt;w@1wt.eu&gt;
Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
Message-ID: &lt;20260509094755.2838-3-w@1wt.eu&gt;
</content>
</entry>
</feed>
