Skip to content

[JPC] Support cve-bf and cve-pre CVE reference formats#39

Merged
bmastbergen merged 1 commit into
mainlinefrom
cve-pre-and-cve-bf-are-ok
Nov 10, 2025
Merged

[JPC] Support cve-bf and cve-pre CVE reference formats#39
bmastbergen merged 1 commit into
mainlinefrom
cve-pre-and-cve-bf-are-ok

Conversation

@bmastbergen

@bmastbergen bmastbergen commented Nov 10, 2025

Copy link
Copy Markdown
Collaborator

Allow commits to reference CVEs using 'cve-bf CVE-YYYY-NNNN' or 'cve-pre CVE-YYYY-NNNN' in addition to the standard 'cve CVE-YYYY-NNNN' format when validating against JIRA VULN tickets. Otherwise we will output a warning for these commits even though they are correctly referencing the CVE from the ticket.

Here is an example of the warnings we get today for 'cve-pre' or 'cve-bf' references:
ctrliq/kernel-src-tree#670 (comment)

Allow commits to reference CVEs using 'cve-bf CVE-YYYY-NNNN' or
'cve-pre CVE-YYYY-NNNN' in addition to the standard 'cve CVE-YYYY-NNNN'
format when validating against JIRA VULN tickets.  Otherwise we will
output a warning for these commits even though they are correctly
referencing the CVE from the ticket.

@thefossguy-ciq thefossguy-ciq left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚤

@bmastbergen bmastbergen merged commit bcb91b2 into mainline Nov 10, 2025
@bmastbergen bmastbergen deleted the cve-pre-and-cve-bf-are-ok branch November 10, 2025 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants