From: Dominique Martinet <asmadeus@codewreck.org>
To: cip-dev@lists.cip-project.org
Cc: Akihito Irie <akihito.irie@atmark-techno.com>,
Dominique Martinet <dominique.martinet@atmark-techno.com>
Subject: Best practices to write CIP kernel details in a SBOM?
Date: Fri, 20 Nov 2026 10:29:20 +0900 [thread overview]
Message-ID: <av-icExXuq2zIc1g@codewreck.org> (raw)
Hi,
I asked about SBOM on IRC a couple of days ago and got told "mailing
list" would be better - I hope I got the right one.. :)
(also note: my org (atmark-techno.com) is not a CIP member as far as I
know, we're not using CIP kernels yet but we do maintain a 5.10 kernel
and I intend to participate at least in reviews/testing starting next
month when upstream 5.10 goes EOL, as I've been doing with upstream 5.10
stable-rc tests. If it's a pre-requisite for discussion please let me
know)
Now for some more useful background and questions...
We're working on improving our SBOM, as it becomes mandatory in various
regulations, and in particular the linux kernel has been difficult to
describe in a useful manner so our users (we ship an OS) can act on the
SBOM.
As long as we stick to upstream kernel stable releases, we can
apparently write PURL/CPE tags as follow:
- pkg:generic/linux-kernel@[version]
- cpe:2.3:o:linux:linux_kernel:[version]:::::::*
and since the linux upstream CVEs are fed to NVD/OSV databases then
scanners will pick up the many CVEs still affecting the releases, so one
can triage them and export the result as VEX as seems to be the current
best practices; but if we don't provide a VEX there doesn't seem to be
any way to describe the kernel version as e.g. v5.10.272-cip79 with all
the fixes covered by CIP automatically covered.
I've found about cip-kernel-sec[1] and kernel-cve-triage[2] and we can
use it to automatically check boxes in a VEX, but would it make sense to
publish this data as well somewhere so that "standard" scanners
(dependency-track/grype/osv-scanner/etc) automatically do it in the
first place?
From what I've seen it's possible to setup a data source for OSV.dev
that they'd pick it up[3], I'm not sure if it'd be useful for CIP as a
project or if it's something that'd gather interest?
[1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec
[2] https://gitlab.com/cip-project/cip-kernel/kernel-cve-triage
[3] https://google.github.io/osv.dev/data/
Just to be clear I'm not asking for free lunch here:
- My main question is, if people here publish a SBOM, what do they use
to describe their kernel to others, is there any recommendation
somewhere I didn't see?
(I saw https://github.com/siemens/debsbom from cip-documents, but
there doesn't seem to be anything about the kernel there)
- Are there any plans going forward for kernel? If so is there anything
we can help with?
Thanks!
--
Dominique Martinet | Asmadeus
next reply other threads:[~2026-11-20 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 1:29 Dominique Martinet [this message]
2026-11-20 12:01 ` Best practices to write CIP kernel details in a SBOM? Christoph Steiger
2026-11-20 12:56 ` [cip-dev] " Dominique Martinet
2026-11-20 13:35 ` Christoph Steiger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=av-icExXuq2zIc1g@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=akihito.irie@atmark-techno.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dominique.martinet@atmark-techno.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox