idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
30,452 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_setadpparms_query_oat_cb(struct qeth_card *card,
struct qeth_reply *reply, unsigned long data)
{
struct qeth_ipa_cmd *cmd;
struct qeth_qoat_priv *priv;
char *resdata;
int resdatalen;
QETH_CARD_TEXT(card, 3, "qoatcb");
cmd = (struct qeth_ipa_cmd *)data;
priv = (struct qeth_qoat_priv *)reply->p... | 307,944,840,202,039,760,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,453 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_setadpparms_set_access_ctrl_cb(struct qeth_card *card,
struct qeth_reply *reply, unsigned long data)
{
struct qeth_ipa_cmd *cmd;
struct qeth_set_access_ctrl *access_ctrl_req;
int fallback = *(int *)reply->param;
QETH_CARD_TEXT(card, 4, "setaccb");
cmd = (struct qeth_ipa_cmd *) data;
access_ctr... | 298,808,039,283,982,320,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,454 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static void qeth_setup_ccw(struct qeth_channel *channel, unsigned char *iob,
__u32 len)
{
struct qeth_card *card;
card = CARD_FROM_CDEV(channel->ccwdev);
QETH_CARD_TEXT(card, 4, "setupccw");
if (channel == &card->read)
memcpy(&channel->ccw, READ_CCW, sizeof(struct ccw1));
else
memcpy(&channel->ccw, WRITE_CC... | 51,023,357,680,709,370,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,455 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_setup_channel(struct qeth_channel *channel)
{
int cnt;
QETH_DBF_TEXT(SETUP, 2, "setupch");
for (cnt = 0; cnt < QETH_CMD_BUFFER_NO; cnt++) {
channel->iob[cnt].data =
kzalloc(QETH_BUFSIZE, GFP_DMA|GFP_KERNEL);
if (channel->iob[cnt].data == NULL)
break;
channel->iob[cnt].state = BUF_STATE_F... | 220,967,300,207,038,960,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,456 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_snmp_command_cb(struct qeth_card *card,
struct qeth_reply *reply, unsigned long sdata)
{
struct qeth_ipa_cmd *cmd;
struct qeth_arp_query_info *qinfo;
struct qeth_snmp_cmd *snmp;
unsigned char *data;
__u16 data_len;
QETH_CARD_TEXT(card, 3, "snpcmdcb");
cmd = (struct qeth_ipa_cmd *) sdata;
dat... | 305,361,714,316,754,650,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,457 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static void qeth_start_kernel_thread(struct work_struct *work)
{
struct task_struct *ts;
struct qeth_card *card = container_of(work, struct qeth_card,
kernel_thread_starter);
QETH_CARD_TEXT(card , 2, "strthrd");
if (card->read.state != CH_STATE_UP &&
card->write.state != CH_STATE_UP)
return;
if (qeth_... | 66,049,487,774,346,670,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,458 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_switch_to_nonpacking_if_needed(struct qeth_qdio_out_q *queue)
{
struct qeth_qdio_out_buffer *buffer;
int flush_count = 0;
if (queue->do_pack) {
if (atomic_read(&queue->used_buffers)
<= QETH_LOW_WATERMARK_PACK) {
/* switch PACKING -> non-PACKING */
QETH_CARD_TEXT(queue->card, 6, "pack->... | 170,051,184,561,091,970,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,459 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static void qeth_switch_to_packing_if_needed(struct qeth_qdio_out_q *queue)
{
if (!queue->do_pack) {
if (atomic_read(&queue->used_buffers)
>= QETH_HIGH_WATERMARK_PACK){
/* switch non-PACKING -> PACKING */
QETH_CARD_TEXT(queue->card, 6, "np->pack");
if (queue->card->options.performance_stats)
queue... | 114,083,730,924,506,320,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,460 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | int qeth_threads_running(struct qeth_card *card, unsigned long threads)
{
unsigned long flags;
int rc = 0;
spin_lock_irqsave(&card->thread_mask_lock, flags);
rc = (card->thread_running_mask & threads);
spin_unlock_irqrestore(&card->thread_mask_lock, flags);
return rc;
}
| 192,075,239,003,284,760,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,461 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | void qeth_trace_features(struct qeth_card *card)
{
QETH_CARD_TEXT(card, 2, "features");
QETH_CARD_TEXT_(card, 2, "%x", card->options.ipa4.supported_funcs);
QETH_CARD_TEXT_(card, 2, "%x", card->options.ipa4.enabled_funcs);
QETH_CARD_TEXT_(card, 2, "%x", card->options.ipa6.supported_funcs);
QETH_CARD_TEXT_(card, 2, ... | 83,396,667,505,094,450,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,462 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_ulp_enable_cb(struct qeth_card *card, struct qeth_reply *reply,
unsigned long data)
{
__u16 mtu, framesize;
__u16 len;
__u8 link_type;
struct qeth_cmd_buffer *iob;
QETH_DBF_TEXT(SETUP, 2, "ulpenacb");
iob = (struct qeth_cmd_buffer *) data;
memcpy(&card->token.ulp_filter_r,
QETH_ULP_E... | 227,274,382,410,510,680,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,463 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static int qeth_ulp_setup_cb(struct qeth_card *card, struct qeth_reply *reply,
unsigned long data)
{
struct qeth_cmd_buffer *iob;
QETH_DBF_TEXT(SETUP, 2, "ulpstpcb");
iob = (struct qeth_cmd_buffer *) data;
memcpy(&card->token.ulp_connection_r,
QETH_ULP_SETUP_RESP_CONNECTION_TOKEN(iob->data),
QET... | 23,278,751,521,476,940,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,464 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static void qeth_unregister_dbf_views(void)
{
int x;
for (x = 0; x < QETH_DBF_INFOS; x++) {
debug_unregister(qeth_dbf[x].id);
qeth_dbf[x].id = NULL;
}
}
| 195,628,423,691,990,400,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,465 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | static void qeth_update_from_chp_desc(struct qeth_card *card)
{
struct ccw_device *ccwdev;
struct channelPath_dsc {
u8 flags;
u8 lsn;
u8 desc;
u8 chpid;
u8 swla;
u8 zeroes;
u8 chla;
u8 chpp;
} *chp_dsc;
QETH_DBF_TEXT(SETUP, 2, "chp_desc");
ccwdev = card->data.ccwdev;
chp_dsc = ccw_device_get_chp... | 229,940,951,130,672,070,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,466 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | struct qeth_cmd_buffer *qeth_wait_for_buffer(struct qeth_channel *channel)
{
struct qeth_cmd_buffer *buffer;
wait_event(channel->wait_q,
((buffer = qeth_get_buffer(channel)) != NULL));
return buffer;
}
| 5,947,641,844,419,897,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,467 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | int qeth_wait_for_threads(struct qeth_card *card, unsigned long threads)
{
if (qeth_is_recovery_task(card))
return 0;
return wait_event_interruptible(card->wait_q,
qeth_threads_running(card, threads) == 0);
}
| 128,757,896,052,755,860,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
30,468 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | int aac_close_fib_context(struct aac_dev * dev, struct aac_fib_context * fibctx)
{
struct fib *fib;
/*
* First free any FIBs that have not been consumed.
*/
while (!list_empty(&fibctx->fib_list)) {
struct list_head * entry;
/*
* Pull the next fib from the fibs
*/
entry = fibctx->fib_list.next;
lis... | 18,772,533,319,214,437,000,000,000,000,000,000,000 | commctrl.c | 60,313,794,856,835,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,469 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | int aac_do_ioctl(struct aac_dev * dev, int cmd, void __user *arg)
{
int status;
/*
* HBA gets first crack
*/
status = aac_dev_ioctl(dev, cmd, arg);
if (status != -ENOTTY)
return status;
switch (cmd) {
case FSACTL_MINIPORT_REV_CHECK:
status = check_revision(dev, arg);
break;
case FSACTL_SEND_LARGE_FI... | 210,780,811,645,026,870,000,000,000,000,000,000 | commctrl.c | 326,718,093,815,197,150,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,470 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | static int check_revision(struct aac_dev *dev, void __user *arg)
{
struct revision response;
char *driver_version = aac_driver_version;
u32 version;
response.compat = 1;
version = (simple_strtol(driver_version,
&driver_version, 10) << 24) | 0x00000400;
version += simple_strtol(driver_version + 1, &driver_ver... | 289,350,171,911,939,680,000,000,000,000,000,000,000 | commctrl.c | 60,313,794,856,835,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,471 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | static int close_getadapter_fib(struct aac_dev * dev, void __user *arg)
{
struct aac_fib_context *fibctx;
int status;
unsigned long flags;
struct list_head * entry;
/*
* Verify that the HANDLE passed in was a valid AdapterFibContext
*
* Search the list of AdapterFibContext addresses on the adapter
* to be... | 240,844,428,115,573,750,000,000,000,000,000,000,000 | commctrl.c | 60,313,794,856,835,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,472 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | static int ioctl_send_fib(struct aac_dev * dev, void __user *arg)
{
struct hw_fib * kfib;
struct fib *fibptr;
struct hw_fib * hw_fib = (struct hw_fib *)0;
dma_addr_t hw_fib_pa = (dma_addr_t)0LL;
unsigned size;
int retval;
if (dev->in_reset) {
return -EBUSY;
}
fibptr = aac_fib_alloc(dev);
if(fibptr == NULL)... | 27,941,302,834,280,960,000,000,000,000,000,000,000 | commctrl.c | 326,718,093,815,197,150,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,473 | linux | b4789b8e6be3151a955ade74872822f30e8cd914 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b4789b8e6be3151a955ade74872822f30e8cd914 | aacraid: prevent invalid pointer dereference
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with fibsize size only but later we
access it until user_srbcmd->sg.count to copy it over to srbcmd.
It is not correct to test (fibsize < sizeof(*user_srbcmd)) because t... | 0 | static int open_getadapter_fib(struct aac_dev * dev, void __user *arg)
{
struct aac_fib_context * fibctx;
int status;
fibctx = kmalloc(sizeof(struct aac_fib_context), GFP_KERNEL);
if (fibctx == NULL) {
status = -ENOMEM;
} else {
unsigned long flags;
struct list_head * entry;
struct aac_fib_context * conte... | 178,441,460,622,312,030,000,000,000,000,000,000,000 | commctrl.c | 60,313,794,856,835,650,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-6380 | The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that tr... | https://nvd.nist.gov/vuln/detail/CVE-2013-6380 |
30,474 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_bcnmiss_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_read(TLV_TYPE_BCNMISS, CMD_SUBSCRIBE_BCNMISS,
file, userbuf, count, ppos);
}
| 199,434,733,860,852,630,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,475 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_bcnmiss_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_BCNMISS, CMD_SUBSCRIBE_BCNMISS,
file, userbuf, count, ppos);
}
| 210,336,861,826,784,360,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,476 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static void lbs_debug_init(struct lbs_private *priv)
{
int i;
if (!priv->debugfs_dir)
return;
for (i = 0; i < num_of_items; i++)
items[i].addr += (size_t) priv;
priv->debugfs_debug = debugfs_create_file("debug", 0644,
priv->debugfs_dir, &items[0],
&lbs_debug_fops);
}
| 146,952,122,161,808,100,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,477 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | void lbs_debugfs_init(void)
{
if (!lbs_dir)
lbs_dir = debugfs_create_dir("lbs_wireless", NULL);
}
| 321,127,306,978,547,000,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,478 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_debugfs_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
int val = 0;
size_t pos = 0;
ssize_t res;
char *p;
int i;
struct debug_data *d;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
p = buf;
d = file... | 139,331,838,558,119,820,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,479 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | void lbs_debugfs_remove_one(struct lbs_private *priv)
{
int i;
for(i=0; i<ARRAY_SIZE(debugfs_regs_files); i++)
debugfs_remove(priv->debugfs_regs_files[i]);
debugfs_remove(priv->regs_dir);
for(i=0; i<ARRAY_SIZE(debugfs_events_files); i++)
debugfs_remove(priv->debugfs_events_files[i]);
debugfs_remove(priv->e... | 98,936,729,589,249,380,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,480 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_dev_info(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
size_t pos = 0;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
ssize_t res;
if (!buf)
return -ENOMEM;
pos += snprintf(buf+pos, le... | 306,879,399,932,510,950,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,481 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_failcount_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_read(TLV_TYPE_FAILCOUNT, CMD_SUBSCRIBE_FAILCOUNT,
file, userbuf, count, ppos);
}
| 255,908,881,540,682,980,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,482 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_failcount_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_FAILCOUNT, CMD_SUBSCRIBE_FAILCOUNT,
file, userbuf, count, ppos);
}
| 83,799,784,772,520,350,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,483 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_highrssi_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_read(TLV_TYPE_RSSI_HIGH, CMD_SUBSCRIBE_RSSI_HIGH,
file, userbuf, count, ppos);
}
| 46,783,878,126,507,865,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,484 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_highrssi_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_RSSI_HIGH, CMD_SUBSCRIBE_RSSI_HIGH,
file, userbuf, count, ppos);
}
| 180,473,715,912,723,870,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,485 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_highsnr_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_SNR_HIGH, CMD_SUBSCRIBE_SNR_HIGH,
file, userbuf, count, ppos);
}
| 318,693,137,460,142,370,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,486 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_host_sleep_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t ret;
size_t pos = 0;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
pos += snprintf(buf,... | 287,430,357,891,251,750,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,487 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_host_sleep_write(struct file *file,
const char __user *user_buf, size_t count,
loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t buf_size, ret;
int host_sleep;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
... | 49,925,329,211,986,800,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,488 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_lowrssi_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_read(TLV_TYPE_RSSI_LOW, CMD_SUBSCRIBE_RSSI_LOW,
file, userbuf, count, ppos);
}
| 117,038,490,787,167,780,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,489 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_lowrssi_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_RSSI_LOW, CMD_SUBSCRIBE_RSSI_LOW,
file, userbuf, count, ppos);
}
| 180,627,866,089,780,520,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,490 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_lowsnr_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_read(TLV_TYPE_SNR_LOW, CMD_SUBSCRIBE_SNR_LOW,
file, userbuf, count, ppos);
}
| 189,479,032,873,464,400,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,491 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_lowsnr_write(struct file *file, const char __user *userbuf,
size_t count, loff_t *ppos)
{
return lbs_threshold_write(TLV_TYPE_SNR_LOW, CMD_SUBSCRIBE_SNR_LOW,
file, userbuf, count, ppos);
}
| 217,262,639,199,924,620,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,492 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdbbp_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t pos = 0;
int ret;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
u32 val;
if (!buf)
return -ENOMEM;
ret = lbs_get_reg... | 223,934,755,622,180,750,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,493 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdbbp_write(struct file *file,
const char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t res, buf_size;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
buf_size = min(... | 80,727,030,915,279,400,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,494 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdmac_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t pos = 0;
int ret;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
u32 val = 0;
if (!buf)
return -ENOMEM;
ret = lbs_get... | 107,805,540,546,866,400,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,495 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdmac_write(struct file *file,
const char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t res, buf_size;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
buf_size = min(... | 29,517,447,866,884,230,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,496 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdrf_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t pos = 0;
int ret;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
u32 val;
if (!buf)
return -ENOMEM;
ret = lbs_get_reg(... | 202,888,178,826,692,900,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,497 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_rdrf_write(struct file *file,
const char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t res, buf_size;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOMEM;
buf_size = min(c... | 42,313,797,739,381,374,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,498 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_sleepparams_read(struct file *file, char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t ret;
size_t pos = 0;
struct sleep_params sp;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOM... | 84,850,834,851,303,025,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,499 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_sleepparams_write(struct file *file,
const char __user *user_buf, size_t count,
loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t buf_size, ret;
struct sleep_params sp;
int p1, p2, p3, p4, p5, p6;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *... | 41,896,739,586,046,750,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,500 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static void *lbs_tlv_find(uint16_t tlv_type, const uint8_t *tlv, uint16_t size)
{
struct mrvl_ie_header *tlv_h;
uint16_t length;
ssize_t pos = 0;
while (pos < size) {
tlv_h = (struct mrvl_ie_header *) tlv;
if (!tlv_h->len)
return NULL;
if (tlv_h->type == cpu_to_le16(tlv_type))
return tlv_h;
length = ... | 317,150,815,749,812,380,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,501 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_wrmac_write(struct file *file,
const char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t res, buf_size;
u32 offset, value;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOM... | 301,863,015,484,797,600,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,502 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_wrrf_write(struct file *file,
const char __user *userbuf,
size_t count, loff_t *ppos)
{
struct lbs_private *priv = file->private_data;
ssize_t res, buf_size;
u32 offset, value;
unsigned long addr = get_zeroed_page(GFP_KERNEL);
char *buf = (char *)addr;
if (!buf)
return -ENOME... | 236,475,398,208,114,800,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
30,503 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int __apic_accept_irq(struct kvm_lapic *apic, int delivery_mode,
int vector, int level, int trig_mode,
unsigned long *dest_map)
{
int result = 0;
struct kvm_vcpu *vcpu = apic->vcpu;
switch (delivery_mode) {
case APIC_DM_LOWEST:
vcpu->arch.apic_arb_prio++;
case APIC_DM_FIXED:
/* FIXME ad... | 118,284,082,963,763,060,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,504 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static u32 __apic_read(struct kvm_lapic *apic, unsigned int offset)
{
u32 val = 0;
if (offset >= LAPIC_MMIO_LENGTH)
return 0;
switch (offset) {
case APIC_ID:
if (apic_x2apic_mode(apic))
val = kvm_apic_id(apic);
else
val = kvm_apic_id(apic) << 24;
break;
case APIC_ARBPRI:
apic_debug("Access APIC A... | 175,533,896,768,009,620,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,505 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int __apic_test_and_clear_vector(int vec, void *bitmap)
{
return __test_and_clear_bit(VEC_POS(vec), (bitmap) + REG_POS(vec));
}
| 218,224,116,306,711,850,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,506 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int __apic_test_and_set_vector(int vec, void *bitmap)
{
return __test_and_set_bit(VEC_POS(vec), (bitmap) + REG_POS(vec));
}
| 297,977,263,271,234,930,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,507 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | void __kvm_migrate_apic_timer(struct kvm_vcpu *vcpu)
{
struct hrtimer *timer;
if (!kvm_vcpu_has_lapic(vcpu))
return;
timer = &vcpu->arch.apic->lapic_timer.timer;
if (hrtimer_cancel(timer))
hrtimer_start_expires(timer, HRTIMER_MODE_ABS);
}
| 290,513,283,673,156,240,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,508 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void __report_tpr_access(struct kvm_lapic *apic, bool write)
{
struct kvm_vcpu *vcpu = apic->vcpu;
struct kvm_run *run = vcpu->run;
kvm_make_request(KVM_REQ_REPORT_TPR_ACCESS, vcpu);
run->tpr_access.rip = kvm_rip_read(vcpu);
run->tpr_access.is_write = write;
}
| 198,408,572,803,845,800,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,509 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_clear_irr(int vec, struct kvm_lapic *apic)
{
apic->irr_pending = false;
apic_clear_vector(vec, apic->regs + APIC_IRR);
if (apic_search_irr(apic) != -1)
apic->irr_pending = true;
}
| 165,565,846,137,683,020,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,510 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_clear_isr(int vec, struct kvm_lapic *apic)
{
if (__apic_test_and_clear_vector(vec, apic->regs + APIC_ISR))
--apic->isr_count;
BUG_ON(apic->isr_count < 0);
apic->highest_isr_cache = -1;
}
| 332,118,064,469,317,550,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,511 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_clear_vector(int vec, void *bitmap)
{
clear_bit(VEC_POS(vec), (bitmap) + REG_POS(vec));
}
| 205,557,226,003,756,260,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,512 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_enabled(struct kvm_lapic *apic)
{
return kvm_apic_sw_enabled(apic) && kvm_apic_hw_enabled(apic);
}
| 297,252,969,611,334,230,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,513 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static u32 apic_get_tmcct(struct kvm_lapic *apic)
{
ktime_t remaining;
s64 ns;
u32 tmcct;
ASSERT(apic != NULL);
/* if initial count is 0, current count should also be 0 */
if (kvm_apic_get_reg(apic, APIC_TMICT) == 0 ||
apic->lapic_timer.period == 0)
return 0;
remaining = hrtimer_get_remaining(&apic->lapic... | 295,923,697,348,172,450,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,514 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int apic_has_pending_timer(struct kvm_vcpu *vcpu)
{
struct kvm_lapic *apic = vcpu->arch.apic;
if (kvm_vcpu_has_lapic(vcpu) && apic_enabled(apic) &&
apic_lvt_enabled(apic, APIC_LVTT))
return atomic_read(&apic->lapic_timer.pending);
return 0;
}
| 333,600,922,893,921,130,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,515 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_lvt_enabled(struct kvm_lapic *apic, int lvt_type)
{
return !(kvm_apic_get_reg(apic, lvt_type) & APIC_LVT_MASKED);
}
| 147,991,913,528,225,900,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,516 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_lvt_nmi_mode(u32 lvt_val)
{
return (lvt_val & (APIC_MODE_MASK | APIC_LVT_MASKED)) == APIC_DM_NMI;
}
| 98,215,540,473,424,230,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,517 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_lvtt_oneshot(struct kvm_lapic *apic)
{
return ((kvm_apic_get_reg(apic, APIC_LVTT) &
apic->lapic_timer.timer_mode_mask) == APIC_LVT_TIMER_ONESHOT);
}
| 200,377,736,914,687,150,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,518 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_lvtt_tscdeadline(struct kvm_lapic *apic)
{
return ((kvm_apic_get_reg(apic, APIC_LVTT) &
apic->lapic_timer.timer_mode_mask) ==
APIC_LVT_TIMER_TSCDEADLINE);
}
| 134,086,949,958,228,370,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,519 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void apic_manage_nmi_watchdog(struct kvm_lapic *apic, u32 lvt0_val)
{
int nmi_wd_enabled = apic_lvt_nmi_mode(kvm_apic_get_reg(apic, APIC_LVT0));
if (apic_lvt_nmi_mode(lvt0_val)) {
if (!nmi_wd_enabled) {
apic_debug("Receive NMI setting on APIC_LVT0 "
"for cpu %d\n", apic->vcpu->vcpu_id);
apic->v... | 145,151,112,612,480,500,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,520 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int apic_mmio_in_range(struct kvm_lapic *apic, gpa_t addr)
{
return kvm_apic_hw_enabled(apic) &&
addr >= apic->base_address &&
addr < apic->base_address + LAPIC_MMIO_LENGTH;
}
| 28,139,803,694,735,863,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,521 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int apic_mmio_read(struct kvm_io_device *this,
gpa_t address, int len, void *data)
{
struct kvm_lapic *apic = to_lapic(this);
u32 offset = address - apic->base_address;
if (!apic_mmio_in_range(apic, address))
return -EOPNOTSUPP;
apic_reg_read(apic, offset, len, data);
return 0;
}
| 29,794,174,025,556,050,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,522 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int apic_reg_read(struct kvm_lapic *apic, u32 offset, int len,
void *data)
{
unsigned char alignment = offset & 0xf;
u32 result;
/* this bitmask has a bit cleared for each reserved register */
static const u64 rmask = 0x43ff01ffffffe70cULL;
if ((alignment + len) > 4) {
apic_debug("KVM_APIC_READ: alignm... | 309,396,553,593,054,340,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,523 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int apic_reg_write(struct kvm_lapic *apic, u32 reg, u32 val)
{
int ret = 0;
trace_kvm_apic_write(reg, val);
switch (reg) {
case APIC_ID: /* Local APIC ID */
if (!apic_x2apic_mode(apic))
kvm_apic_set_id(apic, val >> 24);
else
ret = 1;
break;
case APIC_TASKPRI:
report_tpr_access(apic, true);... | 258,137,042,153,482,760,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,524 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_search_irr(struct kvm_lapic *apic)
{
return find_highest_vector(apic->regs + APIC_IRR);
}
| 231,285,097,975,393,930,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,525 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void apic_send_ipi(struct kvm_lapic *apic)
{
u32 icr_low = kvm_apic_get_reg(apic, APIC_ICR);
u32 icr_high = kvm_apic_get_reg(apic, APIC_ICR2);
struct kvm_lapic_irq irq;
irq.vector = icr_low & APIC_VECTOR_MASK;
irq.delivery_mode = icr_low & APIC_MODE_MASK;
irq.dest_mode = icr_low & APIC_DEST_MASK;
irq.lev... | 194,766,678,283,504,150,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,526 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int apic_set_eoi(struct kvm_lapic *apic)
{
int vector = apic_find_highest_isr(apic);
trace_kvm_eoi(apic, vector);
/*
* Not every write EOI will has corresponding ISR,
* one example is when Kernel check timer on setup_IO_APIC
*/
if (vector == -1)
return vector;
apic_clear_isr(vector, apic);
apic_... | 262,413,083,914,603,400,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,527 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_set_irr(int vec, struct kvm_lapic *apic)
{
apic->irr_pending = true;
apic_set_vector(vec, apic->regs + APIC_IRR);
}
| 247,500,730,033,885,700,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,528 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_set_isr(int vec, struct kvm_lapic *apic)
{
if (!__apic_test_and_set_vector(vec, apic->regs + APIC_ISR))
++apic->isr_count;
BUG_ON(apic->isr_count > MAX_APIC_VECTOR);
/*
* ISR (in service register) bit is set when injecting an interrupt.
* The highest vector is injected. Thus the latest ... | 162,963,715,862,319,260,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,529 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_set_spiv(struct kvm_lapic *apic, u32 val)
{
if ((kvm_apic_get_reg(apic, APIC_SPIV) ^ val) & APIC_SPIV_APIC_ENABLED) {
if (val & APIC_SPIV_APIC_ENABLED)
static_key_slow_dec_deferred(&apic_sw_disabled);
else
static_key_slow_inc(&apic_sw_disabled.key);
}
apic_set_reg(apic, APIC_SPIV, v... | 272,073,745,396,649,430,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,530 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void apic_set_tpr(struct kvm_lapic *apic, u32 tpr)
{
apic_set_reg(apic, APIC_TASKPRI, tpr);
apic_update_ppr(apic);
}
| 18,427,863,726,858,273,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,531 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void apic_set_vector(int vec, void *bitmap)
{
set_bit(VEC_POS(vec), (bitmap) + REG_POS(vec));
}
| 138,165,102,685,296,960,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,532 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void apic_sync_pv_eoi_to_guest(struct kvm_vcpu *vcpu,
struct kvm_lapic *apic)
{
if (!pv_eoi_enabled(vcpu) ||
/* IRR set or many bits in ISR: could be nested. */
apic->irr_pending ||
/* Cache not set: could be safe but we don't bother. */
apic->highest_isr_cache == -1 ||
/* Need EOI... | 89,846,229,926,959,960,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,533 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int apic_test_vector(int vec, void *bitmap)
{
return test_bit(VEC_POS(vec), (bitmap) + REG_POS(vec));
}
| 236,672,798,784,150,800,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,534 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static enum hrtimer_restart apic_timer_fn(struct hrtimer *data)
{
struct kvm_timer *ktimer = container_of(data, struct kvm_timer, timer);
struct kvm_lapic *apic = container_of(ktimer, struct kvm_lapic, lapic_timer);
struct kvm_vcpu *vcpu = apic->vcpu;
wait_queue_head_t *q = &vcpu->wq;
/*
* There is a race windo... | 118,339,677,387,789,760,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,535 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void apic_update_ppr(struct kvm_lapic *apic)
{
u32 tpr, isrv, ppr, old_ppr;
int isr;
old_ppr = kvm_apic_get_reg(apic, APIC_PROCPRI);
tpr = kvm_apic_get_reg(apic, APIC_TASKPRI);
isr = apic_find_highest_isr(apic);
isrv = (isr != -1) ? isr : 0;
if ((tpr & 0xf0) >= (isrv & 0xf0))
ppr = tpr & 0xff;
else
... | 282,255,494,242,096,740,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,536 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static u8 count_vectors(void *bitmap)
{
int vec;
u32 *reg;
u8 count = 0;
for (vec = 0; vec < MAX_APIC_VECTOR; vec += APIC_VECTORS_PER_REG) {
reg = bitmap + REG_POS(vec);
count += hweight32(*reg);
}
return count;
}
| 306,694,429,396,507,400,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,537 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static int find_highest_vector(void *bitmap)
{
int vec;
u32 *reg;
for (vec = MAX_APIC_VECTOR - APIC_VECTORS_PER_REG;
vec >= 0; vec -= APIC_VECTORS_PER_REG) {
reg = bitmap + REG_POS(vec);
if (*reg)
return fls(*reg) - 1 + vec;
}
return -1;
}
| 330,637,281,587,499,740,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,538 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | void kvm_apic_accept_events(struct kvm_vcpu *vcpu)
{
struct kvm_lapic *apic = vcpu->arch.apic;
unsigned int sipi_vector;
unsigned long pe;
if (!kvm_vcpu_has_lapic(vcpu) || !apic->pending_events)
return;
pe = xchg(&apic->pending_events, 0);
if (test_bit(KVM_APIC_INIT, &pe)) {
kvm_lapic_reset(vcpu);
kvm_vc... | 108,627,001,321,145,770,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,539 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_compare_prio(struct kvm_vcpu *vcpu1, struct kvm_vcpu *vcpu2)
{
return vcpu1->arch.apic_arb_prio - vcpu2->arch.apic_arb_prio;
}
| 185,595,253,210,322,000,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,540 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_has_interrupt(struct kvm_vcpu *vcpu)
{
struct kvm_lapic *apic = vcpu->arch.apic;
int highest_irr;
if (!kvm_vcpu_has_lapic(vcpu) || !apic_enabled(apic))
return -1;
apic_update_ppr(apic);
highest_irr = apic_find_highest_irr(apic);
if ((highest_irr == -1) ||
((highest_irr & 0xF0) <= kvm_apic_ge... | 134,308,394,882,470,700,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,541 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline int kvm_apic_id(struct kvm_lapic *apic)
{
return (kvm_apic_get_reg(apic, APIC_ID) >> 24) & 0xff;
}
| 57,296,186,905,749,860,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,542 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_local_deliver(struct kvm_lapic *apic, int lvt_type)
{
u32 reg = kvm_apic_get_reg(apic, lvt_type);
int vector, mode, trig_mode;
if (kvm_apic_hw_enabled(apic) && !(reg & APIC_LVT_MASKED)) {
vector = reg & APIC_VECTOR_MASK;
mode = reg & APIC_MODE_MASK;
trig_mode = reg & APIC_LVT_LEVEL_TRIGGER;
ret... | 161,201,741,399,121,480,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,543 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_match_logical_addr(struct kvm_lapic *apic, u8 mda)
{
int result = 0;
u32 logical_id;
if (apic_x2apic_mode(apic)) {
logical_id = kvm_apic_get_reg(apic, APIC_LDR);
return logical_id & mda;
}
logical_id = GET_APIC_LOGICAL_ID(kvm_apic_get_reg(apic, APIC_LDR));
switch (kvm_apic_get_reg(apic, APIC_D... | 134,907,851,165,962,440,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,544 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_match_physical_addr(struct kvm_lapic *apic, u16 dest)
{
return dest == 0xff || kvm_apic_id(apic) == dest;
}
| 222,892,956,710,717,050,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,545 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | void kvm_apic_nmi_wd_deliver(struct kvm_vcpu *vcpu)
{
struct kvm_lapic *apic = vcpu->arch.apic;
if (apic)
kvm_apic_local_deliver(apic, APIC_LVT0);
}
| 190,019,395,202,645,920,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,546 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | bool kvm_apic_pending_eoi(struct kvm_vcpu *vcpu, int vector)
{
struct kvm_lapic *apic = vcpu->arch.apic;
return apic_test_vector(vector, apic->regs + APIC_ISR) ||
apic_test_vector(vector, apic->regs + APIC_IRR);
}
| 165,573,345,604,905,450,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,547 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | void kvm_apic_post_state_restore(struct kvm_vcpu *vcpu,
struct kvm_lapic_state *s)
{
struct kvm_lapic *apic = vcpu->arch.apic;
kvm_lapic_set_base(vcpu, vcpu->arch.apic_base);
/* set SPIV separately to get count of SW disabled APICs right */
apic_set_spiv(apic, *((u32 *)(s->regs + APIC_SPIV)));
memcpy(vcpu->arch... | 197,279,049,969,661,180,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,548 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | void kvm_apic_set_eoi_accelerated(struct kvm_vcpu *vcpu, int vector)
{
struct kvm_lapic *apic = vcpu->arch.apic;
trace_kvm_eoi(apic, vector);
kvm_ioapic_send_eoi(apic, vector);
kvm_make_request(KVM_REQ_EVENT, apic->vcpu);
}
| 57,763,164,464,196,510,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,549 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void kvm_apic_set_id(struct kvm_lapic *apic, u8 id)
{
apic_set_reg(apic, APIC_ID, id << 24);
recalculate_apic_map(apic->vcpu->kvm);
}
| 221,412,113,672,370,700,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,550 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | int kvm_apic_set_irq(struct kvm_vcpu *vcpu, struct kvm_lapic_irq *irq,
unsigned long *dest_map)
{
struct kvm_lapic *apic = vcpu->arch.apic;
return __apic_accept_irq(apic, irq->delivery_mode, irq->vector,
irq->level, irq->trig_mode, dest_map);
}
| 161,889,815,079,668,530,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
30,551 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static inline void kvm_apic_set_ldr(struct kvm_lapic *apic, u32 id)
{
apic_set_reg(apic, APIC_LDR, id);
recalculate_apic_map(apic->vcpu->kvm);
}
| 219,592,271,517,271,950,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.