[PATCH] cve-check-map: Add 'cannot-backport' to status map

[Dhairya Nagodra <dnagodra@cisco.com>]

- Sometimes, the difference in the codebase of the fixed CVE's version
  and the current version of the package is huge.
- This would make the backporting of the CVE not a feasible option.
- And due to other dependencies and limitations, the upgrade of the
  package might not be possible as well.
- This commit would allow users to add a description via CVE_STATUS and
  still show the CVE as vulnerable.

Signed-off-by: Dhairya Nagodra <dnagodra@cisco.com>
---
 meta/conf/cve-check-map.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/conf/cve-check-map.conf b/meta/conf/cve-check-map.conf
index 17b0f15571..b9df41a6f3 100644
--- a/meta/conf/cve-check-map.conf
+++ b/meta/conf/cve-check-map.conf
@@ -13,6 +13,8 @@ CVE_CHECK_STATUSMAP[fixed-version] = "Patched"
 CVE_CHECK_STATUSMAP[unpatched] = "Unpatched"
 # use when CVE is confirmed by upstream but fix is still not available
 CVE_CHECK_STATUSMAP[vulnerable-investigating] = "Unpatched"
+# use when CVE fix is not compatible to the current version and cannot be backported.
+CVE_CHECK_STATUSMAP[cannot-backport] = "Unpatched"
 
 # used for migration from old concept, do not use for new vulnerabilities
 CVE_CHECK_STATUSMAP[ignored] = "Ignored"