Test PR 3 by espeer · Pull Request #3 · NVIDIA/nova

espeer · 2026-03-20T17:31:24Z

This is a test

Using the Ubuntu configuration on the test branch is a known good general starting point. This configuration will be pared down and refined in future commits in order to reduce build time while still retaining some degree of hardware flexibility for the test cluster. Signed-off-by: Edwin Peer <epeer@nvidia.com>

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Colossus is not presently able to satisfy Hopper leasing requests: Checking leases... 5eca02db-a682-4e5b-8985-576494fd75fc,PROVISIONING,,Nova CI/CD,Blackwell 645aa0fc-bf13-4330-ac6d-4c36da6918d8,PROVISIONING,,Nova CI/CD,Turing 49da4390-7f9b-4f07-a75b-a985a0d15826,PROVISIONING,,Nova CI/CD,Ampere Leasing error: No available pools meet the policy requirements for this lease request Signed-off-by: Edwin Peer <epeer@nvidia.com>

Signed-off-by: Edwin Peer <epeer@nvidia.com>

espeer · 2026-03-20T17:31:43Z

/build

espeer · 2026-03-20T22:53:18Z

/build

espeer · 2026-03-20T23:24:30Z

/build

espeer · 2026-03-23T16:01:23Z

/build

github-actions · 2026-03-23T16:06:51Z

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component	Vulnerability	Description	Severity
Linux Kernel	CVE-2021-46973	In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: Avoid potential use after free in MHI send

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.

As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..|HIGH
Linux Kernel|CVE-2022-2785|There exists an arbitrary memory read within the Linux Kernel BPF - Constants provided to fill pointers in structs passed in to bpf_sys_bpf are not verified and can point anywhere, including memory not owned by BPF. An attacker with CAP_BPF can arbitrarily read memory from anywhere on the system. We recommend upgrading past commit 86f44fc|MEDIUM

espeer · 2026-03-23T23:11:03Z

/build

github-actions · 2026-03-23T23:16:22Z

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component	Vulnerability	Description	Severity
Linux Kernel	CVE-2021-46973	In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: Avoid potential use after free in MHI send

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.

As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..|HIGH
Linux Kernel|CVE-2022-2785|There exists an arbitrary memory read within the Linux Kernel BPF - Constants provided to fill pointers in structs passed in to bpf_sys_bpf are not verified and can point anywhere, including memory not owned by BPF. An attacker with CAP_BPF can arbitrarily read memory from anywhere on the system. We recommend upgrading past commit 86f44fc|MEDIUM

espeer · 2026-03-24T21:11:08Z

/build

github-actions · 2026-03-24T21:16:20Z

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component	Vulnerability	Description	Severity
Linux Kernel	CVE-2021-46973	In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: Avoid potential use after free in MHI send

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.

As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..|HIGH
Linux Kernel|CVE-2022-2785|There exists an arbitrary memory read within the Linux Kernel BPF - Constants provided to fill pointers in structs passed in to bpf_sys_bpf are not verified and can point anywhere, including memory not owned by BPF. An attacker with CAP_BPF can arbitrarily read memory from anywhere on the system. We recommend upgrading past commit 86f44fc|MEDIUM

espeer · 2026-03-24T21:33:18Z

/build

github-actions · 2026-03-24T21:38:07Z

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component	Vulnerability	Description	Severity
Linux Kernel	CVE-2021-46973	In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: Avoid potential use after free in MHI send

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.

As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..|HIGH
Linux Kernel|CVE-2022-2785|There exists an arbitrary memory read within the Linux Kernel BPF - Constants provided to fill pointers in structs passed in to bpf_sys_bpf are not verified and can point anywhere, including memory not owned by BPF. An attacker with CAP_BPF can arbitrarily read memory from anywhere on the system. We recommend upgrading past commit 86f44fc|MEDIUM

magrawal1008 · 2026-03-24T23:46:04Z

/build

espeer · 2026-03-24T23:49:55Z

/build

github-actions · 2026-03-24T23:55:13Z

👎 Promotion blocked, new vulnerability found

Vulnerability report

Component	Vulnerability	Description	Severity
Linux Kernel	CVE-2021-46973	In the Linux kernel, the following vulnerability has been resolved:

net: qrtr: Avoid potential use after free in MHI send

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.

As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..|HIGH
Linux Kernel|CVE-2022-2785|There exists an arbitrary memory read within the Linux Kernel BPF - Constants provided to fill pointers in structs passed in to bpf_sys_bpf are not verified and can point anywhere, including memory not owned by BPF. An attacker with CAP_BPF can arbitrarily read memory from anywhere on the system. We recommend upgrading past commit 86f44fc|MEDIUM

espeer added 9 commits March 20, 2026 17:02

Reduce kernel build configuration

c8b213f

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Create GH workflow

fc3ceaf

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Colossus provisioning

adf91c4

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Nova test branch README

602b24d

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Add Blossom CI hook.

5d63f4b

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Remove legacy GitHub self hosted runner flow.

a75ca68

Signed-off-by: Edwin Peer <epeer@nvidia.com>

Test PR 3

1dff31a

Signed-off-by: Edwin Peer <epeer@nvidia.com>

github-actions bot force-pushed the nova-test branch 3 times, most recently from 4a08a4d to ed21b10 Compare March 23, 2026 04:03

github-actions bot force-pushed the nova-test branch from ed21b10 to e51437e Compare March 24, 2026 03:58

github-actions bot force-pushed the nova-test branch 3 times, most recently from cece59c to 6aafdf2 Compare March 25, 2026 03:58

github-actions bot force-pushed the nova-test branch 6 times, most recently from 1f6f8b6 to 780e8f1 Compare March 31, 2026 04:07

Conversation

espeer commented Mar 20, 2026

Uh oh!

espeer commented Mar 20, 2026

Uh oh!

espeer commented Mar 20, 2026

Uh oh!

espeer commented Mar 20, 2026

Uh oh!

espeer commented Mar 23, 2026

Uh oh!

github-actions bot commented Mar 23, 2026

👎 Promotion blocked, new vulnerability found

Vulnerability report

Uh oh!

espeer commented Mar 23, 2026

Uh oh!

github-actions bot commented Mar 23, 2026

👎 Promotion blocked, new vulnerability found

Vulnerability report

Uh oh!

espeer commented Mar 24, 2026

Uh oh!

github-actions bot commented Mar 24, 2026

👎 Promotion blocked, new vulnerability found

Vulnerability report

Uh oh!

espeer commented Mar 24, 2026

Uh oh!

github-actions bot commented Mar 24, 2026

👎 Promotion blocked, new vulnerability found

Vulnerability report

Uh oh!

magrawal1008 commented Mar 24, 2026

Uh oh!

espeer commented Mar 24, 2026

Uh oh!

github-actions bot commented Mar 24, 2026

👎 Promotion blocked, new vulnerability found

Vulnerability report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants